Are you running over HTTP or HTTPS? We only send the session cookie back over HTTPS.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Wed, Nov 19, 2008 at 2:45 PM, Timothy Tagge <[EMAIL PROTECTED]> wrote: > Hi, > I've configured CAS 3.3.1 and CAS client 2.0.11 to authenticate for > two different webapps running on the same instance of Tomcat 5.5.27. > For now, I've set the Filter for both to /* so that all requests to > those apps need to be authenticated. When going to any URL on App A, > CAS is prompting for a Login. This is expected. After successful > login, the requested page from App A is shown. The problem I'm having > is that linking from App A to App B is causing the CAS login screen to > come up once again. Instead of this behavior, I was expecting that > the user would already be logged in to both App A and App B. Am I > missing something in the documentation, or does CAS not support this > type of configuration? Thanks. > > Tim Tagge > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
