Initial work

Added spring-security-oauth2 as a dependency and added an oauth
configuration spring file inside the spring-configuration folder. Not
sure if it will work the way I expect it since the support is packaged
as a JAR and not a WAR.
In work changes to oauth XML.
Moved configuration file

The config file belongs in src/main/resources. In the webapp file we can
import the configuration from the classpath.
Mappings now take into consideration servlet mappings in web.xml.

For example, the /oauth2.0/* mapping in web.xml redirected a call that
looks like /oauth2.0/authorize to /authorize in the cas servlet context.
Once I realizes that this was happening I changed the custom mapping in
the ouath configuration to take this into account.
In work playing around with configuration

Moved oauth config stuff to securityContext.xml for right now, until I
can figure out why the security stuff in oauth config isn't being
recognized. Added custom user approval endpoint, but it might be
temporary.
Converted to external config

Moved the configuration to the demo project that I'm testing. For now
we're using CustomUserApprovalEndpoint also for testing, but I think we
can re-use existing code with some more work.
Initial Version of new Authentication Provider

This authentication provider is used along side of spring security. Once
this is polished and tested we will have CAS manage the identities and
spring security secure those for those who have ROLE_CAS_USER (in
progress).
Removed unneeded custom class

Now I know that I can use just a ParameterizableViewController in the
XML I can trust that it's unit-tested in spring mvc and focus on the
integration tests.
Added CAS Client Details Service and Error JSP Page

This is just a developer Error JSP page that still needs internationalization and design decisions made. Removed unused logging from the CasServerAuthenticationProvider as well.
Moved grant types into its own definition class
Added CasTokenServices, even though we may not need them. Pending further word from cas devel on this.
Working storage of TGT value based access tokens

We use the token enhancer to remove the UUID generated token value and replace it with the TGT token value. Retrieval still needs work.
In work changes

Refactored client details service authorized grant types to be in the XML file.
Fixed the token enhancer to correctly grab the cas username from the authentication object
Added read ticket support to the cas ticket registry token store.
For now, hard-coded the authorize endpoint to continue to use ParameterizableViewController.
Initial work

Added spring-security-oauth2 as a dependency and added an oauth
configuration spring file inside the spring-configuration folder. Not
sure if it will work the way I expect it since the support is packaged
as a JAR and not a WAR.
In work changes to oauth XML.
Moved configuration file

The config file belongs in src/main/resources. In the webapp file we can
import the configuration from the classpath.
Mappings now take into consideration servlet mappings in web.xml.

For example, the /oauth2.0/* mapping in web.xml redirected a call that
looks like /oauth2.0/authorize to /authorize in the cas servlet context.
Once I realizes that this was happening I changed the custom mapping in
the ouath configuration to take this into account.
In work playing around with configuration

Moved oauth config stuff to securityContext.xml for right now, until I
can figure out why the security stuff in oauth config isn't being
recognized. Added custom user approval endpoint, but it might be
temporary.
Converted to external config

Moved the configuration to the demo project that I'm testing. For now
we're using CustomUserApprovalEndpoint also for testing, but I think we
can re-use existing code with some more work.
Removed unneeded custom class

Now I know that I can use just a ParameterizableViewController in the
XML I can trust that it's unit-tested in spring mvc and focus on the
integration tests.
Fixing line endings

This file was modified by eclipse. I had made some changes to it before, but deleted those changes so the files logically would match. This commit simply points securityContext.xml back to the commit before I touched it.