Thansk Marvin, It wasn't set up so we can rule that out...
Here are my ticketExpirationPolicies.xml (I think it's default) <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:p="http://www.springframework.org/schema/p"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";> <description> Assignment of expiration policies for the different tickets generated by CAS including ticket granting ticket (TGT), service ticket (ST), proxy granting ticket (PGT), and proxy ticket (PT). These expiration policies determine how long the ticket they are assigned to can be used and even how often they can be used before becoming expired / invalid. </description> <!-- Expiration policies --> <bean id="serviceTicketExpirationPolicy" class= "org.jasig.cas.ticket.support.MultiTimeUseOrTimeoutExpirationPolicy"> <!-- This argument is the number of times that a ticket can be used before its considered expired. --> <constructor-arg index="0" value="1" /> <!-- This argument is the time a ticket can exist before its considered expired. --> <constructor-arg index="1" value="300000" /> </bean> <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" /> --> <!-- <constructor-arg index="0" value="300000" /> --> <!-- Set to 3.95 Hours --> <constructor-arg index="0" value="3600000" /> </bean> </beans> and my Ticket Registry Cleaner <!-- TICKET REGISTRY CLEANER --> <bean id="ticketRegistryCleaner" class= "org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner" p:ticketRegistry-ref="ticketRegistry" /> <bean id="jobDetailTicketRegistryCleaner" class= "org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean" p:targetObject-ref="ticketRegistryCleaner" p:targetMethod="clean" /> <bean id="triggerJobDetailTicketRegistryCleaner" class= "org.springframework.scheduling.quartz.SimpleTriggerBean" p:jobDetail-ref="jobDetailTicketRegistryCleaner" p:startDelay="20000" p:repeatInterval="5000000" /> <!-- End TICKET REGISTRY CLEANER --> I don't see anything wrong with it.. But I do rember I used to see entries in the log saying it had run but now I don't.... Chris Whittle SWAT Team Developer J.B. Hunt Transport Services, Inc. Office Phone:(479) 419-3122 Ext:73122 [email protected] No trees were harmed in the sending of this message. A large number of electrons were inconvenienced but recycled From: Marvin Addison <[email protected]> To: [email protected] Date: 03/24/2011 03:33 PM Subject: Re: [cas-dev] TICKETGRANTINGTICKET Table has over a millon rows in it is that normal? > SELECT TOP 10 cast(cast(AUTHENTICATION as varbinary(8000)) as varchar(8000)) > FROM TICKETGRANTINGTICKET > but just got a bunch of "’" Which is what you'd expect for what's contained in that column, a binary blob of data corresponding to the Java serialized data of an ImmutableAuthentication object instance. I don't know what DB platform Ben is using, but it's unusual for a query that simple to work on any platform for binary data. For example, you can't do anything remotely similar on PostgreSQL afaik. In any case if the cast above works, you may be safe to use a LIKE operator on the converted binary data to search for the text REMEMBER_ME like Ben suggested. In any case that's not the best way to determine whether you've enabled the "Remember Me" feature. It's something that has to be explicitly enabled as described at https://wiki.jasig.org/display/CASUM/Remember+Me. If you've done that configuration, it's enabled. It's hard to imagine you've got > 1M SSO sessions caused by that feature unless you have an enormous SSO domain. I imagine it's more likely that you don't have a RegistryCleaner component set up properly to purge orphaned sessions. M -- 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-dev -- 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-dev
