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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,463,370
Community Members
 
Community Events
176
Community Groups

SAML SSO for JIRA Service Desk

We are about to enable SSO with Okta as per 

http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Atlassian-Cloud.html

We need Atlassian and JIRA admins to be excluded from SSO with Okta in case there is an issue with SSO SAML. Should the admin accounts suffixies be aliased with @dominan2.com to avoid the use of SAML SSO?

The users are defined with @domain1.com suffix 

 

1 comment

I set up an account with a gmail address and gave it admin privileges. It turns I never needed it. if you tack /?saml=false to the end of your URL (https://urdomain.atlassian.net/?saml=false), you can log in directly.    

Comment

Log in or Sign up to comment