Perhaps I'm misunderstanding the requirement but... The way some clients handle this is to utilize a application specific cookie for all user authentication after the first. The flow goes something like this: 1. Client browses to secure app for the first time 2. App redirects to CAS because there is no valid "app user cookie" 3. CAS returns a service ticket 4. App validates ST, then sets user specific "app user cookie", and allows access 5. Client returns to app which accepts the passed "app user cookie" as the auth credential and allows access This is a one-time authentication with CAS, to obtain a application specific cookied credential which is used thereafter. mod_auth_cas uses this technique I believe. Dale
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kristin Coles Sent: Friday, 21 December 2007 12:46 p.m. To: [email protected] Subject: Are CAS redirects incompatible with Google web crawler? Hi guys, I have a working Single Sign On solution (which wouldn't have been possible without this forum). However this made our webpages incompatible with Google's web crawler (Googlebot)? When I use "Google Webmaster tools" too see our website logs, I now see thousands of Redirect error messages (which weren't there before the Single Sign On). http://www.google.com/support/webmasters/bin/answer.py?answer=35157 According to the above link, I should "Minimize the number of redirects needed to follow a link from one page to another" to avoid the Redirect error messages. Right now, I am redirecting 3 times for every page visit. 1. Redirect to the CAS server to get a ticket. 2. Redirect back to the page (service url) from the CAS server 3. Self-redirect without the ticket parameter Is this a common problem with a simple solution? Can anyone please tell me how to get over this hurdle. Thank you! Kristin
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
