search

gitlocalize / feedback

:mega: We love feedback :sparkles:
20 stars 8 forks source link

Unable to log into GitLocalized via GitHub SSO #104

Closed shuki25 closed 2 years ago

shuki25 commented 3 years ago

Summary

Unable to log into GitLocalized via GitHub SSO with an error message, "Your GitHub token has expired. Please try to sign in again." It didn't work even after I removed the token from GitHub settings and tried to log in again, still get the same error message.

Steps to reproduce

Previously had an account created 2 years ago and not logged in since a year and half ago before you switched over from User/Password authentication/OAuth to GitHub SSO. When trying to log in, it asks me to link it to GitHub sign in, proceed to approve the permission on GitHub page, redirected back to GitLocalize. It fails afterwards.

Repository URL

(If possible, please paste repository URLs which have errors.)

What is the current bug behavior?

Trying to log in, it redirected me to GitHub to authorize GitLocalize to use GitHub account information. After linking it, it returned to GitLocalize page and got the error message "Your GitHub token has expired. Please try to sign in again". So I tried it again by deleting the token from GitHub and re-authorize, I'm still getting the same error message. I am unable to log into my project. I have some localization work that needs updating. It is a HIGH PRIORITY fix. I have a pull request pending and I can't process it until the log in is fixed.

I think the problem here is that a person with existing account which was created two years ago and did not log in for two years and then tries to log in through GitHub SSO and it failed. There is no way to reset the account whatsoever in order to re-link the account to GitHub SSO.

What is the expected correct behavior?

Should be able to log in without any trouble. You need to have a contingency plan (fail-safe) in case it fails like in my case.

Relevant logs and/or screenshots

image

Possible fixes

(If you have any idea to solve the problem, please help us.)

svasilenkov commented 3 years ago

Thank you for reporting the issue, I've forwarded it to the development team.

svasilenkov commented 2 years ago

@shuki25 The problem has been fixed. Could you please try to log in once again?

shuki25 commented 2 years ago

This issue was resolved after I emailed the support back in April.