We're aiming to get it out by the end of the month. I'll probably cut it on the 29th since that's the weekend.
On Wed, Jan 19, 2011 at 2:30 AM, Moshe Ben-Shoham <[email protected] > wrote: > Hi Scott, > > > > Just saw you resolved CAS-397. Any idea when 3.4.6 will be released? > > > > Thanks, > > Moshe. > > > > *From:* Moshe Ben-Shoham [mailto:[email protected]] > *Sent:* Tuesday, January 18, 2011 9:16 AM > > *To:* [email protected] > *Subject:* RE: [cas-user] Ticket expiration triggers logout of all > services (CAS-686) - why? > > > > Hi Scott, > > > > Thanks for your reply. > > > > I opened https://issues.jasig.org/browse/CAS-937. > > > > Meanwhile, I would like to disable all single signout, as you suggest, but > I don’t know how to do it. The WIKI says “Because not all clients support > single sign out, you may need to disable it at the server level. Each > ArgumentExtractor has a property called "disableSingleSignOut", which if set > to true will make sure the callback does not occur”, but it does not tell me > much. Can you please help? > > > > Thanks, > > Moshe. > > > > *From:* Scott Battaglia [mailto:[email protected]] > *Sent:* Tuesday, January 18, 2011 4:49 AM > *To:* [email protected] > *Subject:* Re: [cas-user] Ticket expiration triggers logout of all > services (CAS-686) - why? > > > > On Sun, Jan 16, 2011 at 4:17 AM, Moshe Ben Shoham < > [email protected]> wrote: > > Hi, > > This is mainly a question to CAS developers. > > CAS-686 was fixed in 3.3.5. I would like to understand the motivation > behind it and maybe override the behavior. > > 1. Why should a user be logged out of an application just because the CAS > ticket expired, which is actually just because he/she did not login to > another application? in the JIRA issue itself ( > https://issues.jasig.org/browse/CAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel#issue-tabs) > it is mentioned that this behavior may not be appropriate to all systems, > yet it was decided to implement it without an apparent way to override it. > Why? > > > > The typical thinking is that if a long-lived ticket has no longer been > used, there is a high likelihood the user has walked away. I can see > however, how that might not be ideal for some people. > > > > > 2. How can I override this behavior? I do not see it is configurable in any > way. I can maybe extend TicketGrantingTicketImpl and implement expire() such > that it does not invoke logOutOfServices(), but I do not see where I can > configure CAS to use my implementation. > > > > Its relatively easy to disable all single log out requests. If you'd just > like to disable it from the registry cleaner, open a ticket and I'll get the > flag to enable/disable into CAS 3.4.6. > > > > Cheers, > > Scott > > > > Thanks in Advance, > Moshe > -- > 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 > > > > The information contained in this message is proprietary to the sender, > protected from disclosure, and may be privileged. The information is > intended to be conveyed only to the designated recipient(s) of the message. > If the reader of this message is not the intended recipient, you are hereby > notified that any dissemination, use, distribution or copying of this > communication is strictly prohibited and may be unlawful. If you have > received this communication in error, please notify us immediately by > replying to the message and deleting it from your computer. Thank you. > > -- > 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 > > > > The information contained in this message is proprietary to the sender, > protected from disclosure, and may be privileged. The information is > intended to be conveyed only to the designated recipient(s) of the message. > If the reader of this message is not the intended recipient, you are hereby > notified that any dissemination, use, distribution or copying of this > communication is strictly prohibited and may be unlawful. If you have > received this communication in error, please notify us immediately by > replying to the message and deleting it from your computer. Thank you. > > -- > 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
