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
I'm using crowd internal user as authentication for Atlassian service like Jira and Confluence.
Now I'd like to switch to external AD, but my concern here that if there exist any potential risk? for example, crowd user create an issue or become an assignee, after AD switch, could Jira recognize the new user in AD if they have the same username. What's the key value for user identification?
Same question for confluence page/space creating and permission inherit.
#data-center #crowd #jira #confluence
Hey @Carlos Chang
We've done a significant amount of work with various Crowd directory types and can confirm the answer in https://community.atlassian.com/t5/Crowd-questions/Crowd-Migrating-from-Crowd-internal-directory-to-Microsoft/qaq-p/131524 is correct. An application connected to Crowd will look at the Application > Directory mapping, and the first instance of a username that matches will be how that user is authenticated. If you have the same username in multiple mapped directories, then all group memberships are merged - eg: if firstname.lastname@example.org is in group A and B in the first directory and B, C and D in the second directory, while they auth against directory 1, the application will see them as being members of groups A,B,C and D
@Carlos Chang I belive this is the answer to your question. https://community.atlassian.com/t5/Crowd-questions/Crowd-Migrating-from-Crowd-internal-directory-to-Microsoft/qaq-p/131524
As with any major change, it is always good to test in a development environment beforehand and backup production prior to making the change.