diff options
| author | Drew Blessing <drew.blessing@me.com> | 2014-04-02 22:11:25 -0500 |
|---|---|---|
| committer | Drew Blessing <drew.blessing@me.com> | 2014-04-10 07:31:54 -0500 |
| commit | 728b05cab7f4bc87cbdc9d1ecb3d54f96ff24ce2 (patch) | |
| tree | 2f36d1c0a8aeec4c39fb130b4bf81a7affc63de9 /doc/integration/github.md | |
| parent | 03472b4fc02a256c90c0285765e7da82c56e93a2 (diff) | |
| download | gitlab-ce-728b05cab7f4bc87cbdc9d1ecb3d54f96ff24ce2.tar.gz | |
Add OmniAuth Documentation
Add GitHub OmniAuth docs
Google instructions
Google instructions
Merge master
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Add Google and Twitter docs
Add screenshot
Add screenshot
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Finalize current docs
Finalize current docs
Add existing user information
Add twitter
Add twitter
Add Twitter disclaimer
Add Twitter disclaimer
remove old doc
Remove unnecessary link
Revert omniauth provider format
Add OmniAuth Documentation
Add GitHub OmniAuth docs
Google instructions
Google instructions
Merge master
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Add Google and Twitter docs
Add screenshot
Add screenshot
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Clean things up
Finalize current docs
Finalize current docs
Add existing user information
Add twitter
Add twitter
Add Twitter disclaimer
Add Twitter disclaimer
remove old doc
Remove unnecessary link
Revert omniauth provider format
Use omniauth again
Remove notice
Restore whitespace
Slight changes
Diffstat (limited to 'doc/integration/github.md')
| -rw-r--r-- | doc/integration/github.md | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/doc/integration/github.md b/doc/integration/github.md new file mode 100644 index 00000000000..672536b4daf --- /dev/null +++ b/doc/integration/github.md @@ -0,0 +1,38 @@ +# GitHub OAuth2 OmniAuth Provider + +To enable the GitHub OmniAuth provider you must register your application with GitHub. GitHub will generate a client ID and secret key for you to use. + +1. Sign in to GitHub. +2. 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. +3. Select "Applications" in the left menu. +4. Select "Register new application". +5. Provide the required details. + * Application name: This can be anything. Consider something like "\<Organization\>'s GitLab" or "\<Your Name\>'s GitLab" or something else descriptive. + * Homepage URL: The URL to your GitLab installation. 'https://gitlab.company.com' + * Application description: Fill this in if you wish. + * Authorization callback URL: 'https://gitlab.company.com/users/auth/github/callback' +6. Select "Register application". +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.  +8. On your GitLab server, open the configuration file. + + ```sh + cd /home/git/gitlab + + sudo -u git -H editor config/gitlab.yml + ``` + +9. Find the section dealing with OmniAuth. See [Initial OmniAuth Configuration](README.md#initial-omniauth-configuration) for more details. +10. Under `providers:` uncomment (or add) lines that look like the following: + + ``` + - { name: 'github', app_id: 'YOUR APP ID', + app_secret: 'YOUR APP SECRET', + args: { scope: 'user:email' } } + ``` + +11. Change 'YOUR APP ID' to the client ID from the GitHub application page from step 7. +12. Change 'YOUR APP SECRET' to the client secret from the GitHub application page from step 7. +13. Save the configuration file. +14. Restart GitLab for the changes to take effect. + +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. If everything goes well the user will be returned to GitLab and will be signed in. |