You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
maybe you can help me:
I have migrated 2 Organisation:
I want to connect users from Orga B to Atlassian Access as well.
I have successfully verified the B-Domain and claimed their users.
However when trying to access the Orga-B via Atlassian-SSO the login does not work:
Due to the URL Error I thought this might be related to "recently" released feature "Authentication policies" atlassian released end of last year (https://support.atlassian.com/security-and-access-policies/docs/understand-authentication-policies/)
Keep in mind OrgaA has been created before October2020 and OrgaB just recently
In general the SAML connection between our IDP and Atlassian works:
When updating e.g. the Email addr in the IDP for a user in OrgaB the Email addr will indeed be updated in the user management.
thanks in advance for your help
Felix
I don't have an answer but have a similar error. We have Okta SSO set up and due to a merger, logins are from two domains (both verified). Users from one can log in but users from the other get the above error. I will file a support case.
Did you get a resolution for this error? - we are also seeing this error
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In our case we had several problems. One was that the AD attribute mapping needed to be different for each org (email, name, etc. weren't stored the same way in the two source directories), so the identity team added some logic like "if domainA.com, pass X to Atlassian else pass Y to Atlassian". Another was that the new IdP feature had to be toggled on by Atlassian for our org. I would reach out to support for this; given that they have added/changed a lot around Access lately (for the better), there could be something non-obvious going on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.