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,459,382
Community Members
 
Community Events
176
Community Groups

How to migrate all users and groups from crowd to other SSO like onelogin

Current Environment:
Jira Datacenter + Crowd + Jira internal Directory.

Trying to migrate to Onelogin.

We are using company email to register users in Jira Datacenter, and onelogin also contains all user emails. 

If we integrate the Jira Datacenter by SAML with Onelogin, will the users match? And how will the user groups be preserved if we turn off Crowd later? 

1 answer

Hey, Han!

Yes, you can migrate users from Crowd to another platform, like Onelogin.


To do that, I can advice you this steps:
1) Export users and groups from Crowd
2) Import users to Onelogin 
3) Configure SAML for Confluence , it should be the same for Jira.
But I should notice, in Crowd you can have multiple groups for one user and in Onelogin I didn't found how you can assign one user to multiple groups, so you need to manage it on Onelogin side.

Also, users should match if you correctly setup how to match them (step #4 from this guide )
And you can easily turn off Crowd later, but you need to make sure that groups with access exists in Jira.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events