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
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
Sporadic user issues signing into Atlassian cloud products, using our SSO idp (ADFS). Seeing different users experience issues with Atlassian only (other SSO sign ins to 3rd party clouds successful). Early indications were it was related to local client time sync, however not able to replicate by manually forcing drift and logging in from my own machine, consistently works.
One user went through SSO and 2FA fine and was rejected, we ran a time sync then retried and they were authed without repeating the SSO logon, suggesting the SAML token was reused form the first attempt and succeeded on the 2nd try. Is there some config in the Atlassian side that allows for time drift we can configure, or something we can do to check the reason for the failures?