Start the article, the Great God Detour.
First, service-side building
The server version I use is: Cas-server-3.4.11-release.zip. After unpacking, rename the \cas-server-3.4.11-release\cas-server-3.4.11\modules\cas-server-webapp-3.4.11.war file to Cas.war, Put it into Tomcat's Tomcat\webapps directory, and then start Tomcat.
Then go to the *****\tomcat\webapps\cas folder and modify the two configuration files:
1. Modify the Tomcat\webapps\cas\web-inf\deployerconfigcontext.xml file:
<bean class= "Org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler" p : httpclient-ref= "HttpClient" p:requiresecure= "false"/>
2. Modify the Tomcat\webapps\cas\web-inf\spring-configuration\ticketgrantingticketcookiegenerator.xml file:
<bean id= "Ticketgrantingticketcookiegenerator" class= " Org.jasig.cas.web.support.CookieRetrievingCookieGenerator "p:cookiesecure=" false "p:cookiemaxage="-1 "p: Cookiename= "CASTGC" p:cookiepath= "/cas"/></beans>
Then enter in the browser: Http://localhost:8099/cas/login, test, open the CAS login page, enter the user name password is 1, to log in. (Cas-serverdefault authentication rule: Authentication is done as long as the user name and password are the same)。
When it appears:
Indicates that the server side is OK.
CAS (central authentication Service)--windows simple setup and testing