Can't login after upgrade to 1.88
-
@klawitterb thanks for the report, I guess we made some mistake in the migration script. I have made it unstable again.
Could it be that you have an external user with the same email as that Cloudron user in GitLab?
@girish I'm only using it myself, so the only accounts active are my own account through LDAP, an admin account and a couple of bots.
-
@klawitterb is the admin's email same as the email in your cloudron account ?
@girish no, admin user has a generic email.
Happy to help debugging if I can do anything, but I'll be on vacation starting tomorrow for a week, so it would have to wait til next week. -
Something went wrong with the OIDC migration in v1.88. I can't login any more. Using Sign in with Cloudron gives me an "Email already in use" error.
Reverted back to v1.87 for now.
@klawitterb said in Can't login after upgrade to 1.88:
Using Sign in with Cloudron gives me an "Email already in use" error.
Does your Cloudron username and email match the username and mail within Gitlab or did you maybe change your mail within Cloudron after creating the corresponding Gitlab account? Most of the time a "Email already in use" error means the app trys to create a new account because the username was not found while login is valid.
Login with Cloudron username + password over OIDC works for me with the current (cloudronapp@1.88.0) version. Maybe you could create another account within Cloudron and give it access to Gitlab.
-
@klawitterb said in Can't login after upgrade to 1.88:
Using Sign in with Cloudron gives me an "Email already in use" error.
Does your Cloudron username and email match the username and mail within Gitlab or did you maybe change your mail within Cloudron after creating the corresponding Gitlab account? Most of the time a "Email already in use" error means the app trys to create a new account because the username was not found while login is valid.
Login with Cloudron username + password over OIDC works for me with the current (cloudronapp@1.88.0) version. Maybe you could create another account within Cloudron and give it access to Gitlab.
-
FYI the changed username fixed it, everything is running fine now.
