Git Lab
Git Lab
To enable the GitLab.com OmniAuth provider you must register your application with GitLab.com.
GitLab.com will generate an application ID and secret key for you to use.
1. Sign in to GitLab.com
Name: This can be anything. Consider something like <Organization>'s GitLab or <Your Name>'s
GitLab or something else descriptive.
Redirect URI:
http://your-gitlab.example.com/import/gitlab/callback
http://your-gitlab.example.com/users/auth/gitlab/callback
The first link is required for the importer and second for the authorization.
6. Select "Submit".
7. You should now see a Client ID and Client Secret near the top right of the page (see screenshot). Keep
this page open as you continue configuration.
(img/gitlab_app.png)
http://gitlab.quipucamayoc.com/help/integration/gitlab 1/2
17/1/2018 Gitlab · Integration · Help · GitLab
cd /home/git/gitlab
gitlab_rails['omniauth_providers'] = [
{
"name" => "gitlab",
"app_id" => "YOUR_APP_ID",
"app_secret" => "YOUR_APP_SECRET",
"args" => { "scope" => "api" }
}
]
11. Change 'YOUR_APP_ID' to the Application ID from the GitLab.com application page.
12. Change 'YOUR_APP_SECRET' to the secret from the GitLab.com application page.
On the sign in page there should now be a GitLab.com icon below the regular sign in form. Click the icon to
begin the authentication process. GitLab.com will ask the user to sign in and authorize the GitLab
application. If everything goes well the user will be returned to your GitLab instance and will be signed in.
http://gitlab.quipucamayoc.com/help/integration/gitlab 2/2