How to re-authorize the OAuth Application 'Git Credential Manager'

Question

I am part of an organization that uses SSO in Github. I don't have problem to access the repository through the web, it redirects me to SSO login and that's all.

The problem started when I logged-in first to my personal repository on GitHub through Git-Bash, I did some changes and then I wanted to do changes in a repository from my organization. When I run the below command, it wrote me that I need to re-authorize the OAuth Application, but I don't understand how:

$ git push --delete origin v0.1.3
remote: The `<my_company>' organization has enabled or enforced SAML SSO. To access
remote: this repository, you must re-authorize the OAuth Application `Git Credential Manager`.
fatal: unable to access 'https://github.com/<my_company>/myproj.git/': The requested URL returned error: 403

How can I re-authorize the login?

I tried to re-open Git-Bash but it wrote me the same error.

If you have "you must re-authorize the ... 'Visual Studio'", then you'll need to remove Visual Studio from your settings here https://github.com/settings/applications, as well as follow the steps below. — thegoodhunter-9115, Jan 24 '23 at 21:19

pmckeown · Accepted Answer · 2021-03-29T04:48:52.470

103

My company just enabled SSO for my Github Org overnight so was getting the same error running git pull. I fixed this with the following steps.

Open Credential Manager in Windows and delete the existing credential for github.com
Re-initialise the cred manager in git bash: git config --global credential.helper manager-core
Re-run git pull and follow the pop-up instructions to authenticate in a browser (which happened automatically for me with SSO).

After those steps git commands worked for me again.

edited Mar 29 '21 at 04:48

answered Mar 04 '21 at 20:22

pmckeown

3,419
3
31
35

I was able to resolve the issue by downloading a legacy version of Chromium browser and setting it to be default browser. The redirect fails at the very end, but I was able to authenticate. – Mark Sep 15 '21 at 18:35
1

For others, be aware that there could be several Github entries in the Windows Credential Manager. Gotta catch 'em all, I guess. – Jacob Foshee Jun 13 '22 at 21:03
In my case I tried using Personal Access Token but it didn't work. I had to re-login via browser. – fiberOptics Oct 06 '22 at 20:33
3

I skipped step 2 and it still worked. – Manish Bansal Dec 13 '22 at 09:42
Instead of step 2, I needed to run `git credential-manager configure` – Wolfgang Kuehn May 06 '23 at 11:55

score 62 · Answer 2 · edited Nov 09 '21 at 20:53

62

I used the Github cli by running the following in the terminal

gh auth login

which then prompted me to re-authenticate, and I was able to.

If you do not have the CLI (Command Line Interface) currently installed, you can visit https://cli.github.com/ for more information. There is a download for Mac.

edited Nov 09 '21 at 20:53

JGallardo

11,074
10
82
96

answered Jun 08 '21 at 18:37

jmazin

1,021
9
11

I saw this reauthorization error after my organization enabled SSO for GitHub Enterprise. This solution worked well for me. When it was complete, I could use the `git` CLI again. When this authN process was running, it prompted me for "GHE hostname". I didn't know what to put, so I just entered "github.com". That turned out to be what I needed. – Mr. Lance E Sloan Jul 22 '22 at 15:18
This is the easiest and best way of fixing the issue. – Mahmut C Sep 02 '22 at 11:13
Note that using `gh auth login` is technically separate from using git credential manager core for authorization. It works, but it uses a different credential management solution (oauth token). – Josh Johanning Mar 21 '23 at 15:15

score 22 · Answer 3 · edited May 17 '23 at 20:15

22

For VSCode users or any other IDE you need to force GitHub to re-authorize the app!

Go to your settings on GitHub.com -> Applications -> Authorized OAuth Apps - https://github.com/settings/applications
Search for "GitHub for VSCode"
Choose "Revoke" from the "..." menu.

If you then sign out in VSCode and sign in again, you should be prompted to re-authorized.

edited May 17 '23 at 20:15

BigBlueHat

2,355
25
30

answered Jan 07 '22 at 15:25

eliarms

551
4
6

1

solution didn't help – Yevhenii Bahmutskyi Feb 07 '23 at 12:59

score 18 · Answer 4 · answered May 19 '21 at 17:41

18

Delete git from "credential manager" window's application. Then pull on repo again. The sso authentication should automatically come up.

answered May 19 '21 at 17:41

Aaron J

341
2
8

1

To clarify, on mac, you can go to the "Keychain Access" app and delete any `git:` login credentials to re-force the git credential manager core login for GitHub. – Josh Johanning Mar 21 '23 at 15:14

score 6 · Answer 5 · answered Jun 23 '22 at 06:07

6

This works for me by revoking the current application in the Github Settings > Settings > Applications > Authorized OAuth Apps

and then try the git pull again.

answered Jun 23 '22 at 06:07

Player1

2,878
2
26
38

score 5 · Answer 6 · answered Mar 13 '23 at 11:56

5

For Visual Studio 2022, Click your profile icon, select Account Settings and then remove and re-add your GitHub credentials

answered Mar 13 '23 at 11:56

BeanFlicker

503
1
9
23

1

thanks a lot!! simple & effective – KKR May 31 '23 at 18:53
This also works for Visual Studio 2019 – Alexandru Dicu Aug 17 '23 at 10:34

score 0 · Answer 7 · answered Jul 29 '23 at 07:49

In Visual studio code, click on profile icon and signout of git. Then login to github, go to settings > Applications > Authorized Oauth Apps. Revoke "VS code" and "Windows Credentials Manager".

In Windows, search for "Credentials Manager" app and delete "git:".

Now clone freshly from VS code and terminal(git clone). Authorize from browser in github. Now, you will re-authorized in both VS Code and command line.

How to re-authorize the OAuth Application 'Git Credential Manager'

7 Answers7