We are in the process of moving our Jira instance from on-prem to off-prem, and our current instance is on-prem which is currently being used and has SSO. But when I try to setup SAML for off-prem (non-prod) it asks me to verify domain, once I am done that - next step is to claim accounts in that organization/domain.
But I am little hesitant to do that as I am unaware of any impact for current user logins(on-prem) so I tried to skip that but looks like it is needed to setup SAML auth. Can anyone help me understand the impact of user logins for our on-prem service?or is there a way that I can skip this claim process as I have few users created by invitation URL's on whom I can test my configuration.
Thanks,
Sravani
Hi @Sravani Kirla ,
No, you need to claim the accounts before you can enable SAML SSO. At a high level, the process is:
1. Verify domain
2. Claim accounts
3. All claimed accounts become "managed" by your organization
4. Enable SSO, which is applied to all your managed accounts.
The purpose of separating out the domain verification step and "claiming" step is so that you knows how many users are going to be claimed and can notify them in advance, since it will trigger an email to users (there's an example of the email in the doc).
Unfortunately it's not currently possible to test SSO with only a few users. The best way to do this is by first verifying a subdomain and inviting a few dummy users that have email addresses tied to that subdomain. (More detail in a previous answer here: https://community.atlassian.com/t5/Atlassian-Access-questions/Re-SAML-Configuration/qaq-p/1178658/comment-id/757#M757)
Hope this helps.
Dave
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.