Please be careful with -1s such that it has specific requirements for its usage. http://www.apache.org/foundation/voting.html
:-) You'll notice that I said the splash page can continue without user interaction (the length of time its displayed is dependent on whether the backend has messages to display to the user). Deployers CAN change those lengths of time. There are a number of reasons for the introduction of the splash page. A few of the more important ones: 1. to allow time to show any messages from the system (i.e. account warnings, global messages, etc.) 2. To show that some form of authentication happened (since some people don't understand SSO and get confused when they're logged into an app automatically). This would be especially key for long term sessions. 3. To clear confusion on when there is a CAS vs. application issue. If you have a better alternative UI flow to solve the above problems (as well as the other ones I can't think of right now ;-)), I think the community (well at least me) would be happy to hear about it. Also, deployers at any point can modify the flow regardless of the UI defaults that WAR provides. It just might not be a pretty merge! Cheers, Scott On Tue, Jul 6, 2010 at 3:47 PM, Marvin Addison <[email protected]>wrote: > > Just a note that for CAS 3.5, we're experimenting with changing the UI > for > > the CAS redirect. Warn will probably no longer be an option. There will > > always be a splash page of variable length depending on whether the CAS > > server has messagse to show. It will also have the option of canceling > (and > > possibly to click through without waiting?). > > > > I'd be curious as to what people think about this idea at the high level. > > -1 > > I _really_ like the control of the warn/splash page being fully under > the control of the user. Not sure exactly what you mean by "click > through without waiting," but there ought to be an option that the > user controls at SSO session start time that would totally bypass the > intermediate page without user interaction. I'm open to the default > behavior changing from "interfere less" to "show more," but ideally > the default behavior to show or hide the splash page would be > configurable by deployers. > > 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
