[BUG] Configuring Taiga to login via GitLab

[nemonik]

Describe the bug

https://github.com/kaleidos-ventures/taiga-docker/#gitlab-settings

As well as, section 1.5 under "Gitlab settings" https://docs.taiga.io/setup-production.html#setup-prod-with-docker

Explains how to configure Taiga to login via GitLab, but this feature when configured does not appear to work nor are the scopes one must configure in GitLab (https://{YOUR-GITLAB}/admin/applications

How can we reproduce the behavior

Configure as your documentation describes with a self hosted GitLab, such as https://github.com/sameersbn/docker-gitlab

Workarounds

N/A

Screenshots

N/A

Taiga environment

Self-hosted. Nothing in logs from tagia-front nor taiga-back.

Arch Linux latest Chrome browser

Additional context

N/A

[nemonik]

🦗 🦗

[tdelatorre]

Hi @nemonik

To add a new application in Gitlab:

1. In the top-right corner, select your avatar and edit profile.
2. In the left sidebar, select Applications.
3. Enter a Name, Redirect URI and read_user scope. The Redirect URI is the URL where users are sent after they authorize with GitLab (your Taiga URL).
4. Select Save application. GitLab displays:
   Application ID
   Secret
   (more info about apps in gitlab here)

Then, set variables in docker-compose.yml and remember change PUBLIC_REGISTER_ENABLED value to "True" (by default is "False") as the documentaton in "1.5. Customisation" explains.

I hope this helps and thanks for you report! We are going to improve this part of the documentation.

[JudgeGregg]

I had to use the following redirect_url in Gitlab: "https://taiga.example.com/login". The "/login" path is not mentioned anywhere in the doc AFAIK. If you could mention it would be great :)

Thank you for your work on Taiga !