Importing JIRA user database to Crowd, documentation question

[Jorge Rojas]

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

[Fabio Racobaldo _Herzum_ · Accepted solution]

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

[Caspar Krieger]

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.