Initial Support for Spring-Security-OAuth2.0

This version depends on building a custom branch of cas that includes
spring security oauth support. This is because of custom endpoints
defined in there. Converted the demo server to use the war overlay
method of including cas server support. At this point we still need to
get the client working.
Removed security context file and added oauth config file\

The oauth config file goes in the unused spring configuration folder, but\
for now we are keeping it in the spring configuration folder for purposes of collaboration.
Separated authentication schemes for different oauth endpoints

The user must be authenticated for the authorize endpoint, while the
client must be authenticated for the token endpoint. The client
authentication can either be HTTP Basic or passed as request parameters
client_id and client_secret.
Cas Client Details Configuration

The client details are now loaded from a cas service manager. Since CAS has no distinction between a client and a user, we use the service manager to define the clients.
Fixed the session expiration issue

The terminate web session listener was killing our session store that held our authorizationRequest for spring-security-oauth. By default it was killing our session in 2 seconds. I commented it out to allow the session to use its default timeout (5 minutes according to web.xml).
After 5 minutes we do get the error page that the authorizationRequest is uninitialized, so it is a bug, just not as huge of a one.
Added 2 entries to the deployer config, but we might as well make it 1 in the future (or 3 explicit endpoints, depending on how secure we need it.)
The OAuth config now is slightly better documented, though there's plenty of room for improvement. Made the c and p namespace attributes more uniform.
Added cas client support for authentication, except for http basic authentication in the resource owner password grant type so the client can provide the client_id and the client_secret in a secure way.
Initial Support for Spring-Security-OAuth2.0

This version depends on building a custom branch of cas that includes
spring security oauth support. This is because of custom endpoints
defined in there. Converted the demo server to use the war overlay
method of including cas server support. At this point we still need to
get the client working.
Removed security context file and added oauth config file\

The oauth config file goes in the unused spring configuration folder, but\
for now we are keeping it in the spring configuration folder for purposes of collaboration.
Separated authentication schemes for different oauth endpoints

The user must be authenticated for the authorize endpoint, while the
client must be authenticated for the token endpoint. The client
authentication can either be HTTP Basic or passed as request parameters
client_id and client_secret.
Cas Client Details Configuration

The client details are now loaded from a cas service manager. Since CAS has no distinction between a client and a user, we use the service manager to define the clients.
Fixed the session expiration issue

The terminate web session listener was killing our session store that held our authorizationRequest for spring-security-oauth. By default it was killing our session in 2 seconds. I commented it out to allow the session to use its default timeout (5 minutes according to web.xml).
After 5 minutes we do get the error page that the authorizationRequest is uninitialized, so it is a bug, just not as huge of a one.
Added 2 entries to the deployer config, but we might as well make it 1 in the future (or 3 explicit endpoints, depending on how secure we need it.)
The OAuth config now is slightly better documented, though there's plenty of room for improvement. Made the c and p namespace attributes more uniform.
Added cas client support for authentication, except for http basic authentication in the resource owner password grant type so the client can provide the client_id and the client_secret in a secure way.
Merge branch 'CAS-1288' of https://github.com/joemccall86/cas-oauth-demo into CAS-1288

Conflicts:
	cas-oauth-server-demo/pom.xml
	cas-oauth-server-demo/src/main/webapp/WEB-INF/cas-servlet.xml
Working changes to utilize enhanced pac4j support

Removed redundancies in the configs and made them match as much as possible to
the originals before they were modified. The spring web project had to be
excluded because of a versioning conflict with another artifact that maven
didn't/couldn't resolve. The oauthConfiguration XML file should be made generic
and placed in the cas unused spring configuration directory in
cas-server-webapp.
Changed name of war file

The war file that's generated is called cas.war. We should look into which one
is right, but for now this is a workaround.
Added authorization to oauthConfig.xml

Originally I had the client credentials configured to determine valid
authorization. For a demo this is hard-coded. The valid usernames are found in
oauthConfiguration.xml.
Merge branch 'CAS-1288'

Conflicts:
	cas-oauth-server-demo/src/main/webapp/WEB-INF/deployerConfigContext.xml
Added correct credentials to the oauth service

and commented out the legacy oauth configuration until it is confirmed that the
new implementation works at least in the same capacity.