Start the article, the Great God Detour.
One. Service-Side Building
The server version number I used 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, Place the Tomcat\webapps folder under Tomcat, and then start Tomcat.
After entering the *****\tomcat\webapps\cas folder, change two configuration files:
1. To change 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. Change 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, to test. Open the CAs login page and enter Usernamepassword to 1 to log in. (Cas-serverdefault validation rule: Only username and password are certified.)。
When it appears:
Indicates that the server side is OK.
CAS (central authentication Service)--windows simple setup and test