-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.4.2: GitLab OAuth doesn't work anymore #24460
Comments
I have the same problem on version 4.4.2. |
I confirm that OAuth authorization does not work |
Hi! What are the versions you upgraded from? this is probably related to #24355 |
@dudanogueira The bug started with version 4.2.2. Now I have updated from 4.4.0. How can i recover Oauth with gitlab |
Can I work on this issue |
@v1adislav can I work on this |
Any news on this?? |
I also have an Internal Server Error during OAuth login with Github after upgrading, I can see the following in the logs:
|
@sampaiodiego mb fix this problem? |
I guess this is also related to #23613 --- which has some workaround that worked for us. |
This is breaking the MacPorts Rocket.Chat instance: https://lists.macports.org/pipermail/macports-users/2022-March/050863.html |
problem resolve in version 4.5.2 |
But the MacPorts Rocket.Chat instance is still broken, though... Edit: downstream issue: https://trac.macports.org/ticket/65937 |
Description:
After upgrading Rocket.Chat to version 4.4.2, OAuth no longer works with GitLab.
You get an undefined error after successful login to our self-managed GitLab instance.
Steps to reproduce:
Actual behavior:
When I try to login I get "Internal server error"
Server Setup Information:
Client Setup Information
Additional context
The GitLab-URL is set to our self hosted GitLab instance.
Relevant logs:
Exception while invoking method 'login' Error: Failed to complete OAuth handshake with gitlab at https://gitlab.com/oauth/token. failed [401] {"error":"invalid_client","error_description":"Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method
The text was updated successfully, but these errors were encountered: