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,467,272
Community Members
 
Community Events
177
Community Groups

Cloud Authentication Policies for Older Orgs

Hello -

I'm looking to use Atlassian Access to configure SAML for my Atlassian org. It's several years old so it does not have authentication policies. I see that there's a "workaround" detailed at this link although I'm not sure what impact following those steps will have on my users.

For example, when I remove my verified domain won't that trigger an email to all of my users saying that their Atlassian accounts are no longer centrally managed? And wouldn't they get another email when the domain gets validated in the new org?

Also, will this change the base URL we use for users to access our Jira and Confluence? ie: will oldorg.atlassian.net change to neworg.atlassian.net?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events