*Background: *We have CAS and LIferay SSO setup. We have tried setting 30
mins time out for CAS* *and Liferay.
*
Problem Statement:* Liferay timeouts after 30 mins but CAS does not. So a
user is not shown the CAS login screen when a user comes after 30 mins of
idle time while liferay shows its time out page perfectly. Why CAS is not
performing timeout correctly? What has been missed and How can this be
achieved ?
*What we want:* After idle time of 30 mins user should be challenged for
credentials from CAS screen.
*What has been done:*
1) Following has been added into web.xml for CAS
(.....webapps/cas/WEB-INF/web.xml)
<!-- Timeout for granting tickets | specified in seconds -->
<context-param>
<param-name>edu.yale.its.tp.cas.grantingTimeout</param-name>
<param-value>1800</param-value>
</context-param>
2) Also along with above change following has been done in conf/web.xml of
tomcat where the CAS is deployed.
<!-- You can set the default session timeout (in minutes) for all newly -->
<!-- created sessions by modifying the value below. | specified in minutes
-->
<session-config>
<session-timeout>30</session-timeout>
</session-config>
When aforementioned didn't work we tried setting service and login timeouts
to 30 mins by following snippet in the web.xml for CAS.
<!-- Timout for service tickets -->
<context-param>
<param-name>edu.yale.its.tp.cas.serviceTimeout</param-name>
<param-value>1800</param-value>
</context-param>
<!-- Timeout for login tickets (since 2.0.12) -->
<context-param>
<param-name>edu.yale.its.tp.cas.loginTimeout</param-name>
<param-value>1800</param-value>
</context-param>
*But to no avail.
Please advise.
*
Regards,
Rahul
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
