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.

  1. On your GitLab server, open the configuration file.

    For omnibus package:

    sudoeditor /etc/gitlab/gitlab.rb

    For installations from source:

    cd/home/git/gitlabsudo-ugit-Heditor config/gitlab.yml
  2. SeeInitial OmniAuth Configurationfor initial settings.

  3. Add the provider configuration:

    For omnibus package:

    gitlab_rails['omniauth_providers']=[{"name"=>"cas3","label"=>“中科院”,"args"=>{"url"=>'CAS_SERVER',"login_url"=>“CAS_PATH /登录”,"service_validate_url"=>'/CAS_PATH/p3/serviceValidate',"logout_url"=>'/CAS_PATH/logout'}}]

    For installations from source:

    ——{名称:“cas3”,label: 'cas',args: {url: 'CAS_SERVER',login_url: '/CAS_PATH/login',service_validate_url: '/CAS_PATH/p3/serviceValidate',logout_url: '/CAS_PATH/logout'} }
  4. Change 'CAS_PATH' to the root of your CAS instance (ie.cas).

  5. If your CAS instance does not use default TGC lifetimes, update thecas3.session_durationto at least the current TGC maximum lifetime. To explicitly disable SLO, regardless of CAS settings, set this to 0.

  6. Save the configuration file.

  7. Reconfigureor重新启动GitLabfor the changes to take effect if you installed GitLab via Omnibus or from source respectively.

On the sign in page there should now be a CAS tab in the sign in form.

Baidu
map