Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×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 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?
Hi @terekha most organizations should have authentication policies now so you can create a separate policy to specifically test your SAML setup without disrupting your users. Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.