Integrate your server with GitLab.com

Import projects from GitLab.com and login to your GitLab instance with your GitLab.com account.

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.

Sign in to GitLab.com
On the upper right corner, click on your avatar and go to your Settings.
Select Applications in the left menu.
Provide the required details for Add new application.
- 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.
Select Save application.
You should now see an Application ID and Secret. Keep this page open as you continue configuration.
On your GitLab server, open the configuration file.

For Omnibus package:
```
sudo editor /etc/gitlab/gitlab.rb
```
For installations from source:
```
cd /home/git/gitlab

sudo -u git -H editor config/gitlab.yml
```
See Initial OmniAuth Configuration for initial settings.

Add the provider configuration:

For Omnibus package:

gitlab_rails['omniauth_providers'] = [
  {
    "name" => "gitlab",
    "app_id" => "YOUR_APP_ID",
    "app_secret" => "YOUR_APP_SECRET",
    "args" => { "scope" => "api" }
  }
]

For installations from source:

- { name: 'gitlab', app_id: 'YOUR_APP_ID',
  app_secret: 'YOUR_APP_SECRET',
  args: { scope: 'api' } }

Change 'YOUR_APP_ID' to the Application ID from the GitLab.com application page.
Change 'YOUR_APP_SECRET' to the secret from the GitLab.com application page.
Save the configuration file.
Reconfigure or restart GitLab for the changes to take effect if you installed GitLab via Omnibus or from source respectively.

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.

2.6 KiB Raw Blame History

Integrate your server with GitLab.com

2.6 KiB

Raw Blame History