Sign in to GitLab with Google or a passkey
The MyLogin.world Bridge runs next to GitLab and sets it up to sign in through MyLogin.world. People choose GitLab’s sign-in button, use Google or a passkey, and come back signed in. GitLab keeps its own accounts and permissions.
- 1
Add the GitLab address
In your dashboard, choose Add a service › GitLab and enter the address you open GitLab at, such as http://192.168.1.30. The command in step 2 fills in as you type.
- 2
Run on the GitLab host Version 2.0.0
Run as root on the host where GitLab runs. It installs the MyLogin.world Bridge for GitLab and configures GitLab, asking before any restart. Linux. Uses Docker when the host has it, otherwise a systemd service.
Review the script ·Source · GPL-3.0-or-later
Download the files
The command picks the right file and checks its SHA-256. To check them yourself:
Intel or AMDamd64mylogin-oidc-2.0.0-linux-amd64b015340b12b1910f487ea32a4aa682944c669abfd409062fa057b9ce449112af64-bit ARMarm64mylogin-oidc-2.0.0-linux-arm641d486bb9f6c505b257f80785fe60ec458af4a41ec1b35ecd76405b007de5547632-bit ARMarmv7mylogin-oidc-2.0.0-linux-armv79898e853d9414b0e5100e5cedcdb97c4eda8a5b71f711864d11cab162b09672cIf the address leads to another machine, such as a proxy, add --host and this host’s address.
- 3
Open GitLab and sign in
Choose “MyLogin.world” on the GitLab sign-in page.
If something fails
On the host, mylogin-oidc gitlab status shows the bridge and its sign-in address, and mylogin-oidc configure gitlab sets GitLab up again. docker logs mylogin-gitlab (or journalctl -u mylogin-oidc@gitlab) shows every request and why a sign-in was refused.
Still stuck? Send us the output: support@mylogin.world.compas.cs.stonybrook.edu.