Support for password authentication was removed on August 13, 2021. Please use a personal access token instead
Asked Answered
A

4

1

Even though I create a PET in GitHub, and I set it in Sourcetree, it does get user, or updated.

Cloning a repo will result the same issue. Why? Should I remove the cache, or what?

enter image description here

Alvaroalveolar answered 10/2, 2022 at 5:10 Comment(0)
A
2

Remove credentials, but not from Keychain as they are not stored there, but from filesystem, as written here:

https://eekayonline.medium.com/connecting-mac-sourcetree-with-your-github-account-b6b3bb3c5a66

home directory > Library > Application Support > Sourcetree

Alvaroalveolar answered 16/2, 2022 at 2:57 Comment(2)
"home directory > Library > Application Support > Sourcetree" doesn't existGiulia
this helped me: https://mcmap.net/q/245205/-source-tree-fix-for-git-password-authentication-is-temporarily-disabled-as-part-of-a-brownout-please-use-a-personal-access-token-instead-duplicateStrained
S
12

Right click the repository name in the selection window and choose convert to SSH.

right click repo and select convert to ssh

Stipendiary answered 14/9, 2022 at 16:3 Comment(1)
If you are using SSH make sure to generate SSH key and add it to your Github account. In Sourcetree settings, Under Account settings use protocol->SSH and save.Indigene
A
2

Remove credentials, but not from Keychain as they are not stored there, but from filesystem, as written here:

https://eekayonline.medium.com/connecting-mac-sourcetree-with-your-github-account-b6b3bb3c5a66

home directory > Library > Application Support > Sourcetree

Alvaroalveolar answered 16/2, 2022 at 2:57 Comment(2)
"home directory > Library > Application Support > Sourcetree" doesn't existGiulia
this helped me: https://mcmap.net/q/245205/-source-tree-fix-for-git-password-authentication-is-temporarily-disabled-as-part-of-a-brownout-please-use-a-personal-access-token-instead-duplicateStrained
A
1

Found here answer:

https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-ignores-github-token-and-throws-403-error/qaq-p/1778978

pen sourcetree, in the right click icon Settings (Repository settings) ->Remotes -> Select Origin and Edit: Set URL/Path in the following format: https://<token>@<git_url>.git

Alvaroalveolar answered 10/2, 2022 at 8:30 Comment(2)
This is generally not the best way to do it, as it leaves the token in cleartext where anyone can see it, and tokens should be protected in the same way as passwords. Instead, update your macOS Keychain, and/or switch to using ssh.Grackle
Thanks a lot, finally a solution that works and does not need 20 minutes of reading lecture.Newsman
R
0

This worked for me:

  1. You need to generate an access token in GitHub
  2. copy it to the clipboard
  3. open keychain access and search for github
  4. Edit the password for Internet password and Web form password keys and replace the current pw with the access token you generated from GitHub
  5. Close and reopen Sourcetree, and try cloning the project again, if pw is requested then enter the access token you have generated.

Source: https://gist.github.com/aeosys/e013268de0e47944abd34d81be13556c

Remissible answered 9/1 at 15:32 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.