Enabling SSO for accounts already existing in Atlassian

[Tristan Yates]

We are looking implement SSO and already have a registered domain and managed user accounts. 

Before we test, i would like to know the behaviour and implications of switching to SAML SSO authentication on top of existing accounts Atlassian-authenticated accounts.

Will our existing user accounts overwritten with new accounts or do they remain in place and matched up with accounts in our SSO infrastructure? 

Just concerned that any attached content remains on the user accounts that will be moved to SSO. 

Also, what are the implications of changing email addresses on our Atlassian managed users so they match their SSO email address? Any considerations I should be aware of? Has anyone done this without issue?

Thank you!

[Bob]

Hi Tristan, 

Without knowing your exact set-up, your SSO solution will most likely identify your Jira users (from whatever User Directory you're using) by matching them with an attribute from your identity provider. Information regarding your Jira users will not be touched. 

If you're using e-mailaddress to identify users, it's obviously important to have them match between Jira and IdP.