Same happened with me. I started trying it with CAS server 3.2. Here is my sequence.
1. I have two servers S1 and S2 2. Have CAS and webapp1 on S1 3. Have webapp2 (a copy of webspp1 with web.xml updated for URLs) on S2 4. Access webapp1, cas authenticates, webapp1/index.jsp opens. 5. access webapp2, webapp2/index.jsp opens as already authenticated. 6. logout from webapp2, cas login page shows up. 7. access webapp1 by typing it in browser address bar, the webapp1/index.jsp opens!! After reading this mail, i downgraded to CAS 3.1.2 (no other changes elsewhere), now it is working. Something got broken in 3.2 or some configuration changes? Thanks, Messi Chan wrote: > Hi, I'm using CAS Client for Java 3.1 and CAS Server3.1.1 in my > project(according to > http://www.ja-sig.org/wiki/display/CASC/CAS+Client+for+Java+3.1 > http://www.ja-sig.org/wiki/display/CASC/CAS+Client+for+Java+3.1 ). It worked > fine. But when I changed CAS Server's version to 3.2, it couldn't > SingleSignOut. What's the difference between them? > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
