Project authentication failure - The thing I never remember when things stop working

Ever since GitHub changed their authentication, I always get stuck on this for some reason...

I set SSH encryption up, and use a GitHub personal access token, nothing particularly exotic.

I use a Mac and save my GitHub credentials in the Keychain. A couple of times a year, the authentication stops working when trying to pull/commit changes in GitHub. Why? I probably am the reason for this, it is easy to mistype a password and click yes on the update password in the Keychain dialog box that pops up briefly if different credentials to the ones present in the keychain are entered, or may be it is something else, who knows...

What follows is the same story every time though: I never remember what to do, fight through the extensive GitHub documentation to try all sorts of steps that are completely unnecessary for this issue, all this takes a few hours of tapping in the dark...

So, this time, as a note to self, and may be as a hint for those who like me get stuck on this from time to time:

Next time it happens, all I need to do is to regenerate my GitHub personal access token, because this is the password that is required in combination with my username,

This is done by

  • going to the top right hand corner of the web browser window when logged on to the GitHub webpage:
    image
  • Clicking on the icon there and choosing the Settings option
  • Clicking on the developer options on the next page:
  • Then choosing "Personal access tokens" on the following page:
    image
  • Then I should be able to regenerate a key, if I don't suddenly remember that I have saved the previous one in a file somewhere...:

If this post is still online in a few months, who knows, it might come in handy....

Happy new Year!

3 Likes