diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-27 00:11:25 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-27 00:11:25 +0300 |
| commit | 9f6c0ac9fd6921bc0b5190ed4d4eaf0ab1e1f2d7 (patch) | |
| tree | 92f397ea19f1fec56491c99ce3b7862bb86fe8ce /doc/integration/cas.md | |
| parent | a56971e97f0385640c2f3568017bd221897b78ef (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration/cas.md')
| -rw-r--r-- | doc/integration/cas.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/integration/cas.md b/doc/integration/cas.md index be54c31ec01..60ce728fa55 100644 --- a/doc/integration/cas.md +++ b/doc/integration/cas.md @@ -6,7 +6,11 @@ info: To determine the technical writer assigned to the Stage/Group associated w # CAS OmniAuth Provider **(FREE)** -To enable the CAS OmniAuth provider you must register your application with your CAS instance. This requires the service URL GitLab supplies 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 back-channel logout. +To enable the CAS OmniAuth provider you must register your application with your +CAS instance. This requires the service URL GitLab supplies to CAS. It should be +something like: `https://gitlab.example.com:443/users/auth/cas3/callback?url`. +Handling for Single Logout (SLO) is enabled by default, so you only have to +configure CAS for back-channel logout. 1. On your GitLab server, open the configuration file. |