Configuring basic CAS integration

Since the Spring Security namespace does not support CAS configuration, there are quite a few more steps that we need to implement in order to get a basic setup working. In order to get a high-level understanding of what is happening, you can refer to the following diagram.

Don't worry about understanding the entire diagram right now, as we will break it into small chunks in order to make it easy to digest:

Creating the CAS ServiceProperties object

The Spring Security setup relies on an o.s.s.cas.ServiceProperties bean in order to store common information about the CAS service. The ServiceProperties object plays a role in coordinating the data exchange between the various CAS components—it is used as a data object to store CAS configuration settings that are shared (and are expected to match) by the varying participants in the Spring CAS stack. You can view the configuration included in the following code snippet:

    //src/main/java/com/packtpub/springsecurity...