Hi, I was looking into the single sign-out feature of the latest CAS client. Our SSO clients are being load-balanced transparently under a single domain. Currently the load-balancer provides sticky sessions. Therefor we don't use session replication over client servers. In a single sign-out scenario the SSO server has no idea which of the client servers provided the client service to a user. Ticket validation appears to be bound to the public outer domain of the services. Is there a known solution to this problem, or do you have any ideas how to get this to work?
Best Regards, Roelof Jan _______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
