On Wed, Dec 21, 2011 at 8:29 AM, Scott Battaglia <[email protected]> wrote: > If the behavior is fixed, I don't see why we should arbitrarily turn > something off that's been active since 2.0 (or earlier) unless we've got > something better.
I don't think anyone has suggested we arbitrarily turn it off. I do think it is wise to evolving CAS in a direction that makes it better, including removing things that no longer make sense. As pointed out on this thread, the WARN feature has marginal value at best and its use case comes from a time before Services Managment whitelist was available and common practice. Removing the checkbox from the default UI for CAS3.5 makes sense to me. This is would be consistent with all the deployments I've worked with recently (Lamar, Principia, Juillard,...), and likely make deploying CAS easier and more enjoyable. Come to think of it, I can't recall a CAS deployment, and I've done many, were folks didn't ask about the check box and then decided they didn't need it. Best, Bill > > > On Tue, Dec 20, 2011 at 6:00 PM, William G. Thompson, Jr. <[email protected]> > wrote: >> >> On Tue, Dec 20, 2011 at 5:44 PM, Steve Swinsburg >> <[email protected]> wrote: >> > Turning it off by default won't fix the underlying issue if people turn >> > it >> > on though. >> >> Sure, still needs to be fixed. I'd say fix the behavior in 3.4.12 and >> make it default to off in 3.5. >> >> Best, >> Bill >> >> > >> > I wondered if there was some way to combine the ST timeout process with >> > checking the CASPRIVACY cookie that a user already gets when they tick >> > that >> > checkbox and working this into the validation flow so the ST doesn't >> > timeout? >> > >> > But it sounds like changing the order of the ST generation might be the >> > best >> > option. >> > >> > cheers, >> > Steve >> > >> > >> > >> > On 21/12/2011, at 8:32 AM, Scott Battaglia wrote: >> > >> > Before we add or drop it, I'd be curious from a UX standpoint, whether >> > the >> > flow can be improved upon. As mentioned before, we made some changes in >> > the >> > CAS4 UI for it that appeared to be an improvement, but hadn't gone >> > through a >> > formal UX review. >> > >> > >> > On Tue, Dec 20, 2011 at 4:24 PM, Marvin Addison >> > <[email protected]> >> > wrote: >> >> >> >> > It makes a lot of sense to me to consider turning this feature off by >> >> > default for CAS 3.5, especially if that just means commenting out the >> >> > mark up in the default UI. >> >> >> >> Whenever this feature comes up I feel like the only one who likes it. >> >> I think there's a valid use case if you have a non-interactive >> >> authentication and you want to provide some user feedback, possibly >> >> with a "don't bother me again" option. >> >> >> >> > Unless there's some groundswell of support for keeping it... >> >> >> >> I'd be open to drafting a proposal to drop it by default if not >> >> altogether and see who complains. >> >> >> >> M >> >> > 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
