Module telescope::web::services::auth::rpi_cas

CAS authentication is implemented roughly following the diagram here and work from RPI students who came before me.

Structs

CAS_USER_REGEX

CasAuthenticatedParameters

Query parameters of the request sent to Telescope after the user is authenticated with RPI CAS.

CasIdentificationParameters

Query parameters sent in request to the CAS endpoint by telescope after the user has authenticated.

RpiCas

Zero-Sized struct representing the RPI CAS identity provider

RpiCasIdentity

The RPI CAS based identity object just stores the user’s RCS id directly. We do not get any other information from the RPI CAS service and the user’s RCS id should never change.

Constants

RPI_CAS_ENDPOINT

The URL of the RPI CAS server.

Functions

cas_authenticated

After the user has authenticated with CAS it will send them back to telescope with a service ticket. This function will extract the service ticket and use it to access the user’s information via CAS. On success, this function return’s the user’s RCS ID as a string (in lowercase).

extract_rcs_id

Use the CAS user id regular expression to extract the RCS ID of a user from the XML returned by the CAS service.

make_authentication_url

Make the url to redirect users to when authenticating.

make_cas_user_regex

Function to make CAS user regular expression.