1

In my office, they have started using single sign on for all Atlassian products, but because of this , those who have cloned git using https have started facing issues. Though it have fixed it by making the clone url as the ssh one, but still i am unable to understand why it happened at the first place?

user11526228
  • 21
  • 2
  • 1
    "...have started facing issues" This is pretty vague. Please [edit] your question to describe the problem in more detail. What issues? What happens when they try? What errors are they getting? – Kenster Mar 03 '21 at 12:35

1 Answers1

0

Using SSH key is one of the solution proposed by How to do Git operations with Bitbucket and SAML SSO

I would also consider using PAT (Personal Access Token), which will act as a password.

That means if a user had cached (using a credential helper) their password instead of the new PAT, said password would no longer work with SSO active: hence the "issues" they were facing.

They need to remove their credentials from the cache, and enter them again (using the PAT as password).

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250