Hi everyone,

I'm fairly new to KDevelop and git and am having a tough time trying to figure out how to clear the stored (via ksshaskpass) credentials used by KDevelop. I accidentally made a mistake entering in those credentials when prompted and also hit the 'remember credentials' button and now I can't use GitHub through KDevelop.

I've researched kasksshpass and found that it tends to store credentials in the KDE Wallet system. However I've looked through my KDE wallet (I only have one) and have no record of the credentials. Also, I've tried to clear git's own credential stores in various locations with no success.

Does anyone know where KDevelop stores GitHub credentials so I can clear them out? Thanks!

As far as I understand the Github Provider doesn't store passwords. It just stores the authentication token it gets back from Github after the first successful login.

So if you want to clear that, go watch out for the KDevelop config file on your local file system and clear out the 'ghprovider' section. The config files are at ~/.config/kdeveloprc (KF5 times) or ~/.kde/share/config/kdeveloprc (KDE4 times).

Hope that solves your problem!

kfunk,

Thanks for that info! It turns out that my problem was because I tried to authenticate two different computers with KDevelop to my Github account. When KDevelop establishes its credentials it automatically creates a Personal Access Token in your Github account named 'KDevelop Github Provider', which KDevelop caches within the file you mentioned ~/.kde/share/config/kdeveloprc. If you then try to authenticate with KDevelop on another machine or after you clear out the token in your already authenticated computer you'll get a rejection from Github because the token already exists. The way to get working is to share the token with all the computers you'll be using by manually entering it into the ~/.kde/share/config/kdeveloprc file on each workstation. If you lose the token you can delete it out of Github and re-create another one via KDevelop as if it's the first time you're authenticating. All the computers will need to be re-synced with the new token after that though. I hope this helps someone else out there... it really took me a long time to figure it out.