Single Sign On¶
In this doc we show an example of how to configure the server to use a Single Sign On or CAS login service to login into Ravada.
In order to authenticate users into Ravada using an external Single Sign On service you need to configure the URL of the external service into ravada.conf YML file.
The config file usually is /etc/ravada.conf. Add this configuration:
sso: url: https://cas.example.com # External CAS Service location service: http://ravada.example.com/login # Ravada Service URL logout: true # Set to also logout from CAS Service when logout from Ravada cookie: priv_key: /etc/ravada/cas/priv_key.pem # Pathname of the private key of the certificate that we will use to generate / validate session cookies pub_key: /etc/ravada/cas/pub_key.pem # Pathname of the public key of the certificate that we will use to generate / validate session cookies type: rsa # Signature algorith: dsa, rsa,... timeout: 36000 # Session cookie lifetime (in seconds
You will need the Authen::ModAuthPubTkt library that can be downloaded from CPAN
sudo cpanm --force Authen::ModAuthPubTkt
How it works¶
When an unauthenticated connection to Ravada is detected, the user is redirected to the CAS service authentication URL.
The CAS service authenticates the user and jumps to the Ravada service address by sending a session ticket as a parameter.
Ravada authenticates the ticket, obtains the user code and generates a session cookie for future user connections (since the ticket can only be authenticated once).