BigW Consortium Gitlab

github.md 5.04 KB
Newer Older
1
# Integrate your server with GitHub
2

3 4
Import projects from GitHub and login to your GitLab instance with your GitHub account.

5
To enable the GitHub OmniAuth provider you must register your application with GitHub.
6
GitHub will generate an application ID and secret key for you to use.
7

8 9 10 11
1.  Sign in to GitHub.

1.  Navigate to your individual user settings or an organization's settings, depending on how you want the application registered. It does not matter if the application is registered as an individual or an organization - that is entirely up to you.

12 13 14
1.  Select "OAuth applications" in the left menu.

1.  If you already have applications listed, switch to the "Developer applications" tab.
15 16 17 18

1.  Select "Register new application".

1.  Provide the required details.
19
    - Application name: This can be anything. Consider something like `<Organization>'s GitLab` or `<Your Name>'s GitLab` or something else descriptive.
20 21
    - Homepage URL: The URL to your GitLab installation. 'https://gitlab.company.com'
    - Application description: Fill this in if you wish.
Xiaogang Wen committed
22
    - Authorization callback URL is 'http(s)://${YOUR_DOMAIN}'. Please make sure the port is included if your Gitlab instance is not configured on default port.
23 24
1.  Select "Register application".

25
1.  You should now see a Client ID and Client Secret near the top right of the page (see screenshot).
26
    Keep this page open as you continue configuration.
27
    ![GitHub app](img/github_app.png)
28 29

1.  On your GitLab server, open the configuration file.
30

31 32 33 34 35 36
    For omnibus package:

    ```sh
      sudo editor /etc/gitlab/gitlab.rb
    ```

37
    For installations from source:
38

39
    ```sh
40
      cd /home/git/gitlab
41

42
      sudo -u git -H editor config/gitlab.yml
43 44
    ```

45
1.  See [Initial OmniAuth Configuration](omniauth.md#initial-omniauth-configuration) for initial settings.
46 47 48 49 50

1.  Add the provider configuration:

    For omnibus package:

Florian committed
51
    For GitHub.com:
52

Florian committed
53 54 55 56 57 58 59 60 61 62
    ```ruby
      gitlab_rails['omniauth_providers'] = [
        {
          "name" => "github",
          "app_id" => "YOUR_APP_ID",
          "app_secret" => "YOUR_APP_SECRET",
          "args" => { "scope" => "user:email" }
        }
      ]
    ```
63

Florian committed
64
    For GitHub Enterprise:
65

66 67 68 69
    ```ruby
      gitlab_rails['omniauth_providers'] = [
        {
          "name" => "github",
70 71
          "app_id" => "YOUR_APP_ID",
          "app_secret" => "YOUR_APP_SECRET",
72
          "url" => "https://github.com/",
73
          "args" => { "scope" => "user:email" }
74 75 76
        }
      ]
    ```
77

78
    For installation from source:
79

80 81 82 83 84 85 86 87 88 89 90
    For GitHub.com:

    ```
      - { name: 'github', app_id: 'YOUR_APP_ID',
        app_secret: 'YOUR_APP_SECRET',
        args: { scope: 'user:email' } }
    ```


    For GitHub Enterprise:

91
    ```
92 93
      - { name: 'github', app_id: 'YOUR_APP_ID',
        app_secret: 'YOUR_APP_SECRET',
94
        url: "https://github.example.com/",
95
        args: { scope: 'user:email' } }
96 97
    ```

98
    __Replace `https://github.example.com/` with your GitHub URL.__
99

100
1.  Change 'YOUR_APP_ID' to the client ID from the GitHub application page from step 7.
101

102
1.  Change 'YOUR_APP_SECRET' to the client secret from the GitHub application page  from step 7.
103

104
1.  Save the configuration file.
105

106
1.  [Reconfigure GitLab][] or [restart GitLab][] for the changes to take effect if you
107
    installed GitLab via Omnibus or from source respectively.
108

109 110
On the sign in page there should now be a GitHub icon below the regular sign in form.
Click the icon to begin the authentication process. GitHub will ask the user to sign in and authorize the GitLab application.
111
If everything goes well the user will be returned to GitLab and will be signed in.
112

113 114 115 116
### GitHub Enterprise with Self-Signed Certificate

If you are attempting to import projects from GitHub Enterprise with a self-signed
certificate and the imports are failing, you will need to disable SSL verification.
117 118
It should be disabled by adding `verify_ssl` to `false` in the provider configuration
and changing the global Git `sslVerify` option to `false` in the GitLab server.
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134

For omnibus package:

```ruby
  gitlab_rails['omniauth_providers'] = [
    {
      "name" => "github",
      "app_id" => "YOUR_APP_ID",
      "app_secret" => "YOUR_APP_SECRET",
      "url" => "https://github.com/",
      "verify_ssl" => false,
      "args" => { "scope" => "user:email" }
    }
  ]
```

135 136 137 138 139 140
You will also need to disable Git SSL verification on the server hosting GitLab.

```ruby
omnibus_gitconfig['system'] = { "http" => ["sslVerify = false"] }
```

141 142 143 144 145 146 147 148 149 150
For installation from source:

```
  - { name: 'github', app_id: 'YOUR_APP_ID',
    app_secret: 'YOUR_APP_SECRET',
    url: "https://github.example.com/",
    verify_ssl: false,
    args: { scope: 'user:email' } }
```

151
You will also need to disable Git SSL verification on the server hosting GitLab.
152 153 154 155 156

```
$ git config --global http.sslVerify false
```

157 158
For the changes to take effect, [reconfigure Gitlab] if you installed
via Omnibus, or [restart GitLab] if you installed from source.
159

160 161
[reconfigure GitLab]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source