Recently my Cody session has expired and it wants me to login again. When I try I get the following:
I’ve tried both Github and Google (both link to the same email). For each, I get the following error:
Another identity for this user from this provider already exists. Remove the link to the other identity from your account.
I’ve tried removing and reinstalling the plugin, as well as clearing the browser cache. Any ideas how I can sign in again? Thanks!
Try with the URL login method and as URL use the https://sourcegraph.com address and with an access token generated in your user profile on Sourcegraph portal.
No luck. The second it opens the web browser and goes to that URL, I get the error message.
Basically I can’t even login to Sourcegraph, even without VSCode. If I simply open up a browser, go to https://sourcegraph.com, click “Login” and choose either Google login or GitHub login, I’ll get that same error.
Okay, I think I got it working again (had to totally clear all browser cookies and cache). I think this is the deal:
I have a GitHub account with two emails: My work email and personal email. My personal email is considered the primary" email.
I have a Cody account that also has those same two emails. However, on my Cody account my work email is the primary.
I can only login to Cody using my work email. If I use Google login with my work Google account, it works. If I use Google login with my personal Google account, I get the error above. If I use GitHub login, it appears to use my personal email by default and I get the error. Also, once I login with my personal account it seems to get in a bad state where I need to clear my browser cache to reset it.
I can login to the portal and create tokens and use those to login anywhere.
What I would like:
Since both my work and personal email addresses are linked to my Cody account, I should be able to login with either work or personal Google SSO or my Github account. If I’m truly not allowed to login with a secondary email address, I should get a more helpful and actionable error message and not be put in a bad state.
Hey @MikeChristensen
Awesome that it works now and clearing the Browser data and cookies did the thing. You are absolutely right, this should be better documented or directly shown at the web page.
