![]() ![]() Then, I went ahead and deleted the existing keychain that was already in the osxkeychain by going into utilities from finder and selecting the Keychain application: I tested this by first unsetting any global value: git config -global -unset credential.helper On OSX it seems you can also use the osxkeychain for the credential.helper. It will go back to the old password and GitHub will refuse it. The question is, how do I make that permanent? Like, how do I put the PAT into the git client cache so I don't have to type it again like before? As of now if I go back to: git config credential.helper store Then I was able to create a GitHub Personal Access Token and use that inside the password field and the new GitHub requirements were satisfied and I didn't get the error. What this did was allow me to enter my username and password again (and not have it supplied by the git client in a tacit way). So what I did was set it like this: git config credential.helper "" I found that it was set to "store" like this: credential.helper=store From that information I inferred that I should check my parameter credential.helper. I sort of solved this problem by looking at this post. ![]() ![]() Remote: Please see for more information.įatal: unable to access '': The requested URL returned error: 403 Please use a personal access token instead. I would get the following message for all private repositories on pull or push: remote: Support for password authentication was removed on August 13, 2021. I learned this only recently because GitHub stopped supporting passwords and instead required Personal Access Tokens (PAT) or SSH keys. I have several repositories which I was apparently using a cached version of password authentication to GitHub. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |