Add link to CAS doc

This commit is contained in:
Douwe Maan 2015-12-21 17:37:55 +01:00
parent 8e3f1fa629
commit 7fc2422c8d
2 changed files with 4 additions and 3 deletions

View File

@ -8,6 +8,7 @@ See the documentation below for details on how to configure these services.
- [LDAP](ldap.md) Set up sign in via LDAP
- [OmniAuth](omniauth.md) Sign in via Twitter, GitHub, GitLab, and Google via OAuth.
- [SAML](saml.md) Configure GitLab as a SAML 2.0 Service Provider
- [CAS](cas.md) Configure GitLab to sign in using CAS
- [Slack](slack.md) Integrate with the Slack chat service
- [OAuth2 provider](oauth_provider.md) OAuth2 application creation
- [Gmail actions buttons](gmail_action_buttons_for_gitlab.md) Adds GitLab actions to messages

View File

@ -1,6 +1,6 @@
# CAS OmniAuth Provider
To enable the CAS OmniAuth provider you must register your application with your CAS instance. This requires the service URL gitlab will supply to CAS. It should be something like: `https://gitlab.example.com:443/users/auth/cas3/callback?url`. By default handling for SLO is enabled, you only need to configure CAS for backchannel logout.
To enable the CAS OmniAuth provider you must register your application with your CAS instance. This requires the service URL GitLab will supply to CAS. It should be something like: `https://gitlab.example.com:443/users/auth/cas3/callback?url`. By default handling for SLO is enabled, you only need to configure CAS for backchannel logout.
1. On your GitLab server, open the configuration file.
@ -10,7 +10,7 @@ To enable the CAS OmniAuth provider you must register your application with your
sudo editor /etc/gitlab/gitlab.rb
```
For instalations from source:
For installations from source:
```sh
cd /home/git/gitlab
@ -59,4 +59,4 @@ To enable the CAS OmniAuth provider you must register your application with your
1. Restart GitLab for the changes to take effect.
On the sign in page there should now be a CAS tab in the sign in form.
On the sign in page there should now be a CAS tab in the sign in form.