diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-20 06:09:15 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-20 06:09:15 +0300 |
commit | b0348fa2727fed578fc53d8d0c6d5f0177c799d5 (patch) | |
tree | bb7138043db1d1d275b8bdb7d55ac986df6cf129 /doc/integration/cas.md | |
parent | 7a84f32e221939059ad4e34c7fecf3633f9ee448 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration/cas.md')
-rw-r--r-- | doc/integration/cas.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/integration/cas.md b/doc/integration/cas.md index e61988c3301..6b8da8ecbd5 100644 --- a/doc/integration/cas.md +++ b/doc/integration/cas.md @@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w # 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 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 backchannel logout. 1. On your GitLab server, open the configuration file. |