You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
in our Crowd
we have a LDAP directory with user Accounts from company A
we have a LDAP directory with user Accounts from company B
User John Doe get group-, Projekt- permissions; create in Jira (Issues, comments etc) and in confluence (sites, likes, comments etc); has space Permissions...
now we have the case that a user move from Company A to Company B.
->credentials form Company A will be deletet
-->new credentials from company B
But if the same User (only with new credentials from Company B) log in into Jira/Confluence> he is a new user with nothing.
is there a Way to assign the "new User" to the Old informations?
If the two LDAP directories use the same naming conventions for usernames then your user would retain content, permissions, etc from the existing account.
If the username will change when the user changes directories, then you may enable an alias in Crowd for each application authenticating through Crowd. In this case you would set the alias for the Directory B username to the name the user had in Directory A.
Details on how to enable aliasing for an application are in this doc: Specifying a User's Aliases
The alias would be on the new account, as a property of the Application in Crowd. It wouldn't rely on the user account existing in Directory A, it would just allow the user to keep using the same username in Confluence: Specifying a User's Aliases:
When logging in to a specific application (e.g. Confluence), Arthur must use the specific username (alias) for that application, e.g. 'arthur'.