Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Can I skip claim accounts step after domain verification for SAML set up?

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.




1 answer

0 votes
Dave Meyer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 13, 2020

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:

Hope this helps.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events