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
One of my users is experiencing an authentication issue after I turned on SSO for my org. Anytime he tries to push, SourceTree is asking him to authenticate. When he enters his domain creds (Azure AD) it tells him that it's incorrect. But he can log into BB just fine. I did a fresh install of SourceTree and was able to authenticate just fine during the setup process. I updated him to the latest version of SourceTree and that didn't help.
Synopsis: When he attempts to perform any Git Push or Pull operation, he gets an Atlassian login prompt. he enters his AD credentials and gets another Atlassian login prompt. he enters his credentials again and then gets a failed authentication message. he attempts to get a new QAuth token but when he does, he gets a Page Not Found error on localhost. he usually uses Sourcetree but to confirm that it was a Git issue. he attempted a Push from the command line and received the same login failure sequence.