Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[transfer-Config] change users' realm when migrating to JFrog SaaS #703

Open
yannc21 opened this issue Mar 8, 2023 · 0 comments
Open

[transfer-Config] change users' realm when migrating to JFrog SaaS #703

yannc21 opened this issue Mar 8, 2023 · 0 comments
Labels
feature request New feature or request

Comments

@yannc21
Copy link

yannc21 commented Mar 8, 2023

Is your feature request related to a problem? Please describe.
When migrating to JFrog SaaS, I'd like the possibility to switch to a new authentication mechanism, for example from LDAP (Self Hosted instance) to SAML SSO (SaaS instance).
For the moment, the Artifactory/Access API don't allow to change a user's realm.

Describe the solution you'd like to see
As the command triggers an Artifactory system export which includes the access export file, the code could modify that file as it contains all the users description

    "username" : "mary",
    "firstName" : null,
    "lastName" : null,
    "email" : "[email protected]",
    "realm" : "ldap",
    "status" : "enabled",

new params could be added such as --src-realm=ldap and --target-realm=saml which will replace any occurence of ldap by saml

Describe alternatives you've considered
the JFrog official recommendation is to ask each "ldap" user to log on the JFrog Platform via SAML which will either recreate their user in the target realm (like SAML) if the username is different from the initial one (ldap) or override the realm of the user if the login is the same for ldap and saml.

Additional context
NA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant