Generally, you rely on the CAS Gateway solution and the supporting clients which are smart enough to check only once per session. However, gatewaying, does require one redirect per application to check for the user.
-Scott On Tue, Mar 10, 2009 at 3:13 PM, Cliff Ingham <[email protected]>wrote: > Is there a way to avoid redirecting all non-authenticated users to > the CAS server to check to see if they're logged on? > > I have multiple web applications, all are publicly accessible. However if > you authenticate, you see more stuff on each screen. I don't have seperate > secure resources. > > If a user authenticates to APP1, then opens a new browser window and > browsers to APP2, what should I be doing on APP2 to check to see if the user > has already authenticated? > > All the solutions I'm seeing involve redirecting all non-authenticated > users to the CAS server to see if they're authenticated. I don't want to be > redirecting all web requests to another server. That's a lot of > redirecting! > > -- > 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
