Sso demo cancels https (cas) and ssohttps

Sso demo cancels https (cas) and ssohttps

Basic configuration refer to the previous http://www.cnblogs.com/rocky-fang/p/5354947.html

1. Modify tomcat-cas Configuration

1.1 find deployerConfigContext. xml in the path D: \ test \ sso \ tomcat-cas \ webapps \ cas \ WEB-INF as follows: (add p: requireSecure = "false ")

 <bean id="proxyAuthenticationHandler"          class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler"          p:httpClient-ref="httpClient" p:requireSecure="false" />

1.2 D: \ test \ sso \ tomcat-cas \ webapps \ cas \ WEB-INF \ spring-configuration find ticketGrantingTicketCookieGenerator. xml modify as follows: (modify p: cookieSecure = "true ")

    <bean id="ticketGrantingTicketCookieGenerator" class="org.jasig.cas.web.support.CookieRetrievingCookieGenerator"        p:cookieSecure="false"        p:cookieMaxAge="-1"        p:cookieName="CASTGC"        p:cookiePath="/cas" />

1.3 D: \ test \ sso \ tomcat-cas \ webapps \ cas \ WEB-INF \ spring-configuration find warnCookieGenerator. xml modify as follows: (modify p: cookieSecure = "true ")

<bean id="warnCookieGenerator" class="org.jasig.cas.web.support.CookieRetrievingCookieGenerator"        p:cookieSecure="false"

When the cas server is running, it can only use http requests, saving the trouble of configuring the HTTPS protocol.