gitlab oauth is broken because scope is not sent #1497

New Issue

GiteaMirror · 2025-11-02T04:02:33-06:00

GiteaMirror commented

2025-11-02 04:02:33 -06:00

Originally created by @captn3m0 on GitHub (Feb 2, 2018).

Gitea version (or commit ref): gitea/gitea:1.3.2
Git version: 2.13.5
Operating system: linux/amd64. Running using docker
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant (gitlab is not present as a authentication mechanism)
Log gist:

Description

GitLab OAuth does not work because scope is not sent as part of the authentication redirect. You can verify the issue on my gitea instance: https://git.captnemo.in/user/oauth2/gitlab

Screenshots

Gitea Config

GitLab App config

Originally created by @captn3m0 on GitHub (Feb 2, 2018).  - Gitea version (or commit ref): `gitea/gitea:1.3.2` - Git version: `2.13.5` - Operating system: linux/amd64. Running using docker - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant (gitlab is not present as a authentication mechanism) - Log gist: ## Description GitLab OAuth does not work because scope is not sent as part of the authentication redirect. You can verify the issue on my gitea instance: <https://git.captnemo.in/user/oauth2/gitlab> ## Screenshots ### Login Error at GitLab ![image](https://user-images.githubusercontent.com/584253/35748603-9315a9f6-0874-11e8-9924-1acc85310b34.png) ### Gitea Config ![image](https://user-images.githubusercontent.com/584253/35748619-ab6c2106-0874-11e8-94dc-df918546147c.png) ### GitLab App config ![image](https://user-images.githubusercontent.com/584253/35748671-d5a5a780-0874-11e8-9de9-16aa4319ac84.png)

GiteaMirror added the type/bug label 2025-11-02 04:02:33 -06:00

GiteaMirror closed this issue

2025-11-02 04:02:34 -06:00

GiteaMirror commented

2025-11-02 04:02:34 -06:00

@captn3m0 commented on GitHub (Feb 2, 2018):

Upgraded to the 1.4 docker image and the issue persists.

@captn3m0 commented on GitHub (Feb 2, 2018): Upgraded to the `1.4` docker image and the issue persists.

GiteaMirror commented

2025-11-02 04:02:34 -06:00

@internalfx commented on GitHub (Jun 11, 2018):

I can confirm this issue on my system as well

@internalfx commented on GitHub (Jun 11, 2018): I can confirm this issue on my system as well

GiteaMirror commented

2025-11-02 04:02:35 -06:00

@techknowlogick commented on GitHub (Jun 28, 2018):

@captn3m0 I've just created a PR to pass the scope, however have you tried using OpenID Connect? I found that worked for me. The openid connect URL for gitlab is https://gitlab.com/.well-known/openid-configuration

@techknowlogick commented on GitHub (Jun 28, 2018): @captn3m0 I've just created a PR to pass the scope, however have you tried using OpenID Connect? I found that worked for me. The openid connect URL for gitlab is https://gitlab.com/.well-known/openid-configuration

GiteaMirror commented

2025-11-02 04:02:35 -06:00

@captn3m0 commented on GitHub (Jun 29, 2018):

Haven't tried it as I'm the only active user on my server.

Thanks a lot for the PR 🥇

@captn3m0 commented on GitHub (Jun 29, 2018): Haven't tried it as I'm the only active user on my server. Thanks a lot for the PR :1st_place_medal:

GiteaMirror commented

2025-11-02 04:02:35 -06:00

@clarfonthey commented on GitHub (Jun 30, 2018):

Also running into this problem.

@clarfonthey commented on GitHub (Jun 30, 2018): Also running into this problem.

GiteaMirror referenced this issue