You should not be resetting the Service Ticket expiration policy so that it never expires. Those tickets MUST expire whether its due to time or their one-time use.
Service Tickets should not be used as a way to access TicketGrantingTickets. In fact, no one outside of the CentralAuthenticationService class should be accessing the Service Ticket (which is why that interface never returns a ServiceTicket). -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Jun 24, 2008 at 1:47 PM, Axel Mendoza Pupo <[EMAIL PROTECTED]> wrote: > Its no imposible but it is not the TGT the value that you need, it is the > service ticket value. the service ticket value is send it to apps as a > result of authentication, then apps may to stablish a connection to CAS to > validate it. The service ticket in CAS has a reference to a > ticketGrantingTicketImpl that has the TGT value it self or this > ticketGrantingTicketImpl have another ticketGrantingTicketImpl reference > that has the TGT value. My point is that you dont need to set any ticket > policy other than NeverExpiresExpirationPolicy to handle the timeout by > yourself, but to do this you need to add your own code because CAS don't > provide anything like this and some code need to be add in apps to send the > service ticket value to maintain the session. > > All of this was explained before but it seem that nobody care. > CAS did not support global timeout so you need to do it by yourself. > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
