Hi, since upgrading to Ventura I’m having to constantly enter my credentials to connect to github - generally daily as its not remembering them for some reason.
When checking in the keychain app the entry is being removed.
Any ideas anyone?
thx
Hi, since upgrading to Ventura I’m having to constantly enter my credentials to connect to github - generally daily as its not remembering them for some reason.
When checking in the keychain app the entry is being removed.
Any ideas anyone?
thx
Hello, this is Gulshan Negi.
Well, I searched about it on Google, and I found that there are a few things you can do to fix the problem if you find that you are constantly having to enter your Github credentials in Ventura and that the keychain entry is being removed. These include changing your Github password, checking your keychain settings and permissions, checking your Github settings, and getting in touch with Github support if you need to. By taking these steps, you should be able to resolve the issue and connect to Github seamlessly in Ventura.
Thanks
I’m not really an expert in github but I wonder if this happens regardless of the git client that you are using.
Do you get the same problem if you interact with git on the command line? Do you use some GUI client for Git or do you rely on Xcode for that?
i’m using command line to access git. will contact github support i think, but very strange that something is actually removing the key from the keychain without my permission…
I was lazy and gave up ![]()
brew install gh
gh auth login
gh auth setup-git
that’s it.
They’ll probably just tell you to use SSH keys, as I assume you’re not currently using them given you have to give GitHub credentials (I’ve never had to do that, but I use SSH keys exclusively).
i’m using personal access tokens, which is what I’ve been using for the last couple of years. never had a problem on windows or mac until I upgraded to Ventura a week or so ago.
Oh, this is a new one for me. tbh I’ve also had issues with macOS and using SSH keys even, Apple changing things as they like to do, but it just required some minor change to re-enable the thing they disabled! ![]()
Interesting, I see the same issue with Azure DevOps since about a week (after all, it’s both Microsoft). Had to re-enter my credentials two or three times since last week. I’ve been on Ventura for some time, so it seems to be more of a server-side change to a much shorter expiry time or something?
not sure - the token from github is set to never expire.
When viewing the entry created in the keychain it has no expirty date on it, so I don’t understand why they are being removed.
Just had a keychain entry that lasted about 3 hours!
thx - this appears to have fixed the issue!