Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,485
Community Members
 
Community Events
176
Community Groups

Crowd user identification

Hi guys,

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

3 answers

1 vote

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 user@example.com 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

CCM

1 vote
Brant Schroeder Community Leader May 19, 2021

@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.  

@Brant Schroeder Thank you for the info, I've get the idea but still have some questions and I leave comments in the thread.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events