Additional CAS capabilities

CAS offers additional advanced configuration capabilities outside of those that are exposed through the Spring Security CAS wrappers. Some of these include the following capabilities:

• Providing transparent SSO for users who are accessing multiple CAS- secured applications within a configurable time window on the CAS server.
• Applications can force users to authenticate to CAS by setting the renew property to true on TicketValidator; you may want to conditionally set this property in some custom code in the event that the user attempts to access a highly secured area of the application.
• A RESTful API for obtaining service tickets.
• The Aperero CAS server can also act as an OAuth2 server. If you think about it, this makes sense, since CAS is very similar to OAuth2.
• Providing OAuth support for the CAS server so that it can obtain access tokens to a delegate OAuth provider (that is, Google), or so the CAS server can be the OAuth server...