Presented by Adam Rybicki at Jasig 2010 in San Diego, CA
Recording courtesy of TechSmith
CAS uses Spring Web Flow to do "script" processing of login and ticket validation protocol. This presentation will discuss how to extend CAS by injecting business logic into CAS Web Flow. This allows extending CAS without having to modify any CAS code.
The presentation will illustrate how to add a new Web Flow state. This state checks for the user having accepted the university's "Accepted Use Policy." This is a policy that every user has to accept once a year. The date of the last policy acceptance is stored in LDAP.
Another example of extending CAS this way is to check for password change. Many universities have a policy to require periodic password changes. This enhancement checks the last password change date, and if it has been too long since the last password change, the user is forced to change the password. Both examples prevent the users from authenticating to services until they are satisfied. Both the password change and policy acceptance application are themselves CAS-enabled.
This presentation details how normal CAS flow is changed to force the users to perform these steps before they are allowed to log in. Upon satisfying both applications, normal CAS behavior is restored.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?