Add SAML support via Omniauth
This commit is contained in:
Alex Lossent
parent
4146ce559e
commit
22de5443c5
7 changed files with 104 additions and 0 deletions
|
|
@ -22,6 +22,7 @@ v 7.12.0 (unreleased)
|
|||
- Prefix EmailsOnPush email subject with `[Git]`.
|
||||
- Group project contributions by both name and email.
|
||||
- Clarify navigation labels for Project Settings and Group Settings.
|
||||
- Add SAML support as an omniauth provider
|
||||
|
||||
v 7.11.2
|
||||
- no changes
|
||||
|
|
|
|||
1
Gemfile
1
Gemfile
|
|
@ -31,6 +31,7 @@ gem 'omniauth-shibboleth'
|
|||
gem 'omniauth-kerberos', group: :kerberos
|
||||
gem 'omniauth-gitlab'
|
||||
gem 'omniauth-bitbucket'
|
||||
gem 'omniauth-saml'
|
||||
gem 'doorkeeper', '2.1.3'
|
||||
gem "rack-oauth2", "~> 1.0.5"
|
||||
|
||||
|
|
|
|||
12
Gemfile.lock
12
Gemfile.lock
|
|
@ -333,6 +333,8 @@ GEM
|
|||
rb-fsevent (>= 0.9.3)
|
||||
rb-inotify (>= 0.9)
|
||||
lumberjack (1.0.4)
|
||||
macaddr (1.7.1)
|
||||
systemu (~> 2.6.2)
|
||||
mail (2.6.3)
|
||||
mime-types (>= 1.16, < 3)
|
||||
method_source (0.8.2)
|
||||
|
|
@ -389,6 +391,9 @@ GEM
|
|||
omniauth-oauth2 (1.1.1)
|
||||
oauth2 (~> 0.8.0)
|
||||
omniauth (~> 1.0)
|
||||
omniauth-saml (1.3.1)
|
||||
omniauth (~> 1.1)
|
||||
ruby-saml (~> 0.8.1)
|
||||
omniauth-shibboleth (1.1.1)
|
||||
omniauth (>= 1.0.0)
|
||||
omniauth-twitter (1.0.1)
|
||||
|
|
@ -523,6 +528,9 @@ GEM
|
|||
rainbow (>= 1.99.1, < 3.0)
|
||||
ruby-progressbar (~> 1.4)
|
||||
ruby-progressbar (1.7.1)
|
||||
ruby-saml (0.8.2)
|
||||
nokogiri (>= 1.5.0)
|
||||
uuid (~> 2.3)
|
||||
ruby2ruby (2.1.3)
|
||||
ruby_parser (~> 3.1)
|
||||
sexp_processor (~> 4.0)
|
||||
|
|
@ -606,6 +614,7 @@ GEM
|
|||
stamp (0.5.0)
|
||||
state_machine (1.2.0)
|
||||
stringex (2.5.2)
|
||||
systemu (2.6.5)
|
||||
task_list (1.0.2)
|
||||
html-pipeline
|
||||
temple (0.6.7)
|
||||
|
|
@ -654,6 +663,8 @@ GEM
|
|||
raindrops (~> 0.7)
|
||||
unicorn-worker-killer (0.4.2)
|
||||
unicorn (~> 4)
|
||||
uuid (2.3.7)
|
||||
macaddr (~> 1.0)
|
||||
version_sorter (2.0.0)
|
||||
virtus (1.0.1)
|
||||
axiom-types (~> 0.0.5)
|
||||
|
|
@ -757,6 +768,7 @@ DEPENDENCIES
|
|||
omniauth-gitlab
|
||||
omniauth-google-oauth2
|
||||
omniauth-kerberos
|
||||
omniauth-saml
|
||||
omniauth-shibboleth
|
||||
omniauth-twitter
|
||||
org-ruby (= 0.9.12)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,7 @@
|
|||
class OmniauthCallbacksController < Devise::OmniauthCallbacksController
|
||||
|
||||
protect_from_forgery except: [:kerberos, :saml]
|
||||
|
||||
Gitlab.config.omniauth.providers.each do |provider|
|
||||
define_method provider['name'] do
|
||||
handle_omniauth
|
||||
|
|
|
|||
|
|
@ -210,6 +210,15 @@ production: &base
|
|||
# args: { scope: 'api' } }
|
||||
# - { name: 'bitbucket', app_id: 'YOUR_APP_ID',
|
||||
# app_secret: 'YOUR_APP_SECRET'}
|
||||
# - { name: 'saml',
|
||||
# args: {
|
||||
# assertion_consumer_service_url: 'https://gitlab.example.com/users/auth/saml/callback',
|
||||
# idp_cert_fingerprint: '43:51:43:a1:b5:fc:8b:b7:0a:3a:a9:b1:0f:66:73:a8',
|
||||
# idp_sso_target_url: 'https://login.example.com/idp',
|
||||
# issuer: 'https://gitlab.example.com',
|
||||
# name_identifier_format: 'urn:oasis:names:tc:SAML:2.0:nameid-format:transient'
|
||||
# } }
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -75,6 +75,7 @@ Now we can choose one or more of the Supported Providers below to continue confi
|
|||
- [Google](google.md)
|
||||
- [Shibboleth](shibboleth.md)
|
||||
- [Twitter](twitter.md)
|
||||
- [SAML](saml.md)
|
||||
|
||||
## Enable OmniAuth for an Existing User
|
||||
|
||||
|
|
|
|||
77
doc/integration/saml.md
Normal file
77
doc/integration/saml.md
Normal file
|
|
@ -0,0 +1,77 @@
|
|||
# SAML OmniAuth Provider
|
||||
|
||||
GitLab can be configured to act as a SAML 2.0 Service Provider (SP). This allows GitLab to consume assertions from a SAML 2.0 Identity Provider (IdP) such as Microsoft ADFS to authenticate users.
|
||||
|
||||
First configure SAML 2.0 support in GitLab, then register the GitLab application in your SAML IdP:
|
||||
|
||||
1. Make sure GitLab is configured with HTTPS. See [Using HTTPS](../install/installation.md#using-https) for instructions.
|
||||
|
||||
1. On your GitLab server, open the configuration file.
|
||||
|
||||
For omnibus package:
|
||||
|
||||
```sh
|
||||
sudo editor /etc/gitlab/gitlab.rb
|
||||
```
|
||||
|
||||
For instalations from source:
|
||||
|
||||
```sh
|
||||
cd /home/git/gitlab
|
||||
|
||||
sudo -u git -H editor config/gitlab.yml
|
||||
```
|
||||
|
||||
1. See [Initial OmniAuth Configuration](omniauth.md#initial-omniauth-configuration) for initial settings.
|
||||
|
||||
1. Add the provider configuration:
|
||||
|
||||
For omnibus package:
|
||||
|
||||
```ruby
|
||||
gitlab_rails['omniauth_providers'] = [
|
||||
{
|
||||
"name" => "saml",
|
||||
args: {
|
||||
assertion_consumer_service_url: 'https://gitlab.example.com/users/auth/saml/callback',
|
||||
idp_cert_fingerprint: '43:51:43:a1:b5:fc:8b:b7:0a:3a:a9:b1:0f:66:73:a8',
|
||||
idp_sso_target_url: 'https://login.example.com/idp',
|
||||
issuer: 'https://gitlab.example.com',
|
||||
name_identifier_format: 'urn:oasis:names:tc:SAML:2.0:nameid-format:transient'
|
||||
}
|
||||
}
|
||||
]
|
||||
```
|
||||
|
||||
For installations from source:
|
||||
|
||||
```yaml
|
||||
- { name: 'saml',
|
||||
args: {
|
||||
assertion_consumer_service_url: 'https://gitlab.example.com/users/auth/saml/callback',
|
||||
idp_cert_fingerprint: '43:51:43:a1:b5:fc:8b:b7:0a:3a:a9:b1:0f:66:73:a8',
|
||||
idp_sso_target_url: 'https://login.example.com/idp',
|
||||
issuer: 'https://gitlab.example.com',
|
||||
name_identifier_format: 'urn:oasis:names:tc:SAML:2.0:nameid-format:transient'
|
||||
} }
|
||||
```
|
||||
|
||||
1. Change the value for 'assertion_consumer_service_url' to match the HTTPS endpoint of GitLab (append 'users/auth/saml/callback' to the HTTPS URL of your GitLab installation to generate the correct value).
|
||||
|
||||
1. Change the values of 'idp_cert_fingerprint', 'idp_sso_target_url', 'name_identifier_format' to match your IdP. Check [the omniauth-saml documentation](https://github.com/PracticallyGreen/omniauth-saml) for details on these options.
|
||||
|
||||
1. Change the value of 'issuer' to a unique name, which will identify the application to the IdP.
|
||||
|
||||
1. Restart GitLab for the changes to take effect.
|
||||
|
||||
1. Register the GitLab SP in your SAML 2.0 IdP, using the application name specified in 'issuer'.
|
||||
|
||||
To ease configuration, most IdP accept a metadata URL for the application to provide configuration information to the IdP. To build the metadata URL for GitLab, append 'users/auth/saml/metadata' to the HTTPS URL of your GitLab installation, for instance:
|
||||
```
|
||||
https://gitlab.example.com/users/auth/saml/metadata
|
||||
```
|
||||
|
||||
At a minimum the IdP *must* provide a claim containing the user's email address, using claim name 'email' or 'mail'. The email will be used to automatically generate the GitLab username. GitLab will also use claims with name 'name', 'first_name', 'last_name' (see [the omniauth-saml gem](https://github.com/PracticallyGreen/omniauth-saml/blob/master/lib/omniauth/strategies/saml.rb) for supported claims).
|
||||
|
||||
On the sign in page there should now be a SAML button below the regular sign in form. Click the icon to begin the authentication process. If everything goes well the user will be returned to GitLab and will be signed in.
|
||||
|
||||
Loading…
Reference in a new issue