Thanks William! Do you know if there is a way to force renew=true at CAS server instead of configuring it in all my client applications?
Thanks in advance! ________________________________ From: "William G. Thompson, Jr." <[email protected]> To: [email protected] Sent: Sunday, May 29, 2011 9:59 AM Subject: Re: [cas-user] SSO - Behavior in http / https On Sat, May 28, 2011 at 8:05 AM, Fernando Correa <[email protected]> wrote: > I've already found the answer for my first question. This behavior could be > generated by using renew parameter. Am I correct? Yes, you should also look at Gateway behavior. http://www.jasig.org/cas/client-integration/gateway > Still having doubts with the second... > What about "With this mode, when I do a redirect > to https://casserver/logout from webapp2, it seems that it cleans my ticket > (I see "ACTION: TICKET_GRANTING_TICKET_DESTROYED" in CAS Server log), and > webapps doesn't still available to create PTs.". A logout in one application > avoids me to generate new PTs in the portal. Redirecting to cas/logout kills the CAS SSO session (independent of any Application Session), including any PGTs. If you just want to log out of the webapp2, then you shouldn't redirect to cas/logout. Bill -- 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 -- 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
