Skip to main content

Code Libraries

Texas A&M's CAS deployment returns the standard payload so CAS client code from the Apereo Foundation site can be used.

Published CAS Libraries​

LanguageLibrary
PHPDownload
PythonDownload
.NETDownload
JavaDownload

Parameter Customization​

The Service Provider's CAS code may include one or more of the following parameters:

  • service - The Service Provider identifier, usually the URL of the Service Provider site. CAS will redirect the Subject back to the URL upon completion of a successful authentication event. If this parameter is not included, CAS displays a message notifying the Subject that they have successfully logged in.
info

Example: https://server/cas/login?service=https%3A%2F%2FmySite.edu

  • renew - Boolean value indicating whether or not the Service Provider wants to bypass Single Sign-On. This value is defaulted to False, so the renew parameter is required only when it should be set to True. When set to False, CAS checks for an existing session (managed using the cookie storing the Ticket Granting Ticket) for the Subject. Only when the Subject does not have an active session does CAS require a credential to be presented.
tip

When renew is set to True, CAS requests a credential regardless of whether or not an active session exists.

Example: https://server/cas/login?service=http%3A%2F%2FmySite.edu&renew=true

  • gateway - Boolean value indicating whether or not the Service Provider wants CAS to only check for a Single-Sign On session. This value is defaulted to False, so the gateway parameter is required only when it should be set to True.
info

The gateway parameter is used for landing pages, where the Subject is not required to be authenticated to view content. This parameter allows sites to customize page content depending on whether or not a Single Sign-On session exists.

Example: https://server/cas/login?service=http%3A%2F%2FmySite.edu&gateway=true