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,467,527
Community Members
 
Community Events
177
Community Groups

Importing JIRA user database to Crowd, documentation question

I am trying to migrate from a JIRA User DB to Crowd SSO, but am having trouble picking between ATLASSIAN-SHA1 and ATLASSIAN-SECURITY in the setup. The two links below mention different selections, one being SHA1 and another being SECURITY. Can someone clarify which one I should use to ensure compatibility?

https://confluence.atlassian.com/display/CROWD/Configuring+an+Internal+Directory

https://confluence.atlassian.com/display/CROWD/Importing+Users+from+Atlassian+JIRA

1 answer

1 accepted

1 vote
Answer accepted

Hello Jorge,

"ATLASSIAN-SECURITY has effectively superceded ATLASSIAN-SHA1. I'm going to run through and update the documentation where it's out of date, but if at any point you're directed to select ATLASSIAN-SHA1 and the only option is ATLASSIAN-SECURITY, that's what to go for."

https://answers.atlassian.com/questions/37406/crowd-password-encryption-no-atlassian-sha1-option

Hope this helps,

Fabio

This is correct. To give some more information, ATLASSIAN-SECURITY is a special password encoder which will fall back to treating the passwords as SHA1 encoded if the normal verification process fails (and then proceed to upgrade the SHA1 password to the normal hashing scheme if the password is valid according to the SHA1 hash saved in the database). In other words, a password that's valid according to ATLASSIAN-SHA1 will also be valid for ATLASSIAN-SECURITY.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events