Hi, Carlos, What you're seeing is normal. You're logging in to two different URLs (https://server1 and https://server2), and the Tomcat session* and CAS TGC are stored in browser cookies, so each server won't see the other server's cookies. The servers must be accessed through a common URL, which usually involves placing them behind a load balancer or some other clustering service -- assigning two DNS address records with both servers' IP addresses for the same hostname will be sufficient for testing purposes in a pinch. Your cas.properties must contain that common hostname.
Best regards, -- (other) Carlos. * Yes, the session ID could be carried in the URI, but I don't wanna deal with that. -----Original Message----- From: Carlos [mailto:[email protected]] Sent: Thursday, 13 June, 2013 04:53 To: [email protected] Subject: [cas-user] Cluster with tomcat session replicate Hi, I have a question about cluster of CAS 3.5.2. My environment is: - 2 Server with tomcat 6.0.37, - CAS 3.5.2 with JPA Ticket Registry on postgresql. The cluster CAS Servers are configured about https://wiki.jasig.org/display/CASUM/Clustering+CAS. The Tomcats no error in Catalina.out. The question is: When I go to https://server1:8443/cas, I logged. But, when I open a new tab in web browser, I go to http://server2:8443/cas I need logged again. * This is normal??. * I should be logged in server2 because I logged in server1??. Thank's -- 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
