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 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?
"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."
Hope this helps,
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.