...
By default these tickets are configured to expire after 7,200,000 milliseconds == 7,200 seconds == 2 hours.
| Code Block |
|---|
| xml | xml |
|---|
| title | ticketExpirationPolicies.xml default configuration of ticket granting ticket timeout of 2 hours |
|---|
| xml |
|---|
|
<bean id="grantingTicketExpirationPolicy" class="org.jasig.cas.ticket.support.TimeoutExpirationPolicy">
<!-- This argument is the time a ticket can exist before its considered expired. -->
<constructor-arg
index="0"
value="7200000" />
</bean>
|
Suppose you'd prefer ticket granting tickets remain valid for 45 minutes == 2,700 seconds == 2,700,000 milliseonds before expiring. Here's how you'd configure that:
| Code Block |
|---|
xml |
|---|
| xml |
|---|
| title | ticketExpirationPolicies.xml changed configuration of ticket granting ticket timeout to 45 minutes |
|---|
| xml |
|---|
|
<bean id="grantingTicketExpirationPolicy" class="org.jasig.cas.ticket.support.TimeoutExpirationPolicy">
<!-- This argument is the time a ticket can exist before its considered expired. -->
<constructor-arg
index="0"
value="2700000" />
</bean>
|
This timeout is independent of the CAS web application session timeout, which is only important for keeping user place in the login workflow. That timeout is configured in the CAS webapp web.xml and defaults configured to five minutes:
| Code Block |
|---|
xml |
|---|
| xml |
|---|
| title | Default configuration in CAS server web.xml of five minute application session timeout |
|---|
| xml |
|---|
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
...
<session-config>
<!-- Default to 5 minute session timeouts -->
<session-timeout>5</session-timeout>
</session-config>
...
</web-app>
|
...