Turning it off by default won't fix the underlying issue if people turn it on though.
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 > > -- > 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 -- 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
