You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to connect my Google account so I can log in with that, but I have apparently accidentally created a separate metacpan account that can log in with the Google account.
When I log in with github, I'm in the account I've always had, and the button next to the Google link for connecting an account is red. When I click it to add that connection, I'm immediately redirected back from Google's oauth page (because metacpan is already allowed to access the requested info) but am now logged into a different metacpan account which has only the Google account attached (now the github account button is green, for example).
Can these two accounts be merged? Can you prevent this from happening in the future?
The text was updated successfully, but these errors were encountered:
You're not the first to have issues, though I'm a little confused by your description.
When I log in with github, I'm in the account I've always had, and the button next to the Google link for connecting an account is red. When I click it to add that connection
If it's red, it should mean you're already logged in (red => Disconnect, green => Connect).
I wanted to connect my Google account so I can log in with that, but I have apparently accidentally created a separate metacpan account that can log in with the Google account.
When I log in with github, I'm in the account I've always had, and the button next to the Google link for connecting an account is red. When I click it to add that connection, I'm immediately redirected back from Google's oauth page (because metacpan is already allowed to access the requested info) but am now logged into a different metacpan account which has only the Google account attached (now the github account button is green, for example).
Can these two accounts be merged? Can you prevent this from happening in the future?
The text was updated successfully, but these errors were encountered: