Hi, Our team has successfully implemented CAS with EhCache for ticket registry/replication on our test environment(two servers T1 and T2 behind the load-balancer) and everything seems to be working fine until we encountered an issue with one of our vendor application(which has its custom login page). At sometimes, after the authentication is successful and TGT is created, instead of being redirected to the dashboard it is being redirected to the default CAS login page.
Observation with simple Java App: ``````````````````````````` We tried repeating this with a simple java application(casified) and it never did this. TGT and ST are created on the same server and ST is validated on either of the servers successfully and is redirected to the dashboard page. Observation with Vendor App: ``````````````````````` Sometimes the TGT and ST are created on the same server(one of the two servers behind the load-balancer) and everything seems to be working fine. Sometime the only TGT is created on one of the servers and we see ST in failed to create on another server. TGT should have been replicated by EhCache and ST should not fail to get created on the other server too. I am assume that because of the above observation, it is redirecting to the default CAS login page and from there everything is happening properly. I am not sure if this is with the vendor application which has a custom login page. I didn't implement StickySessions and still other applications work properly and it is only with this application. If anyone has undergone this kind of an issue please help me out to resolve this. Thanks, Sandeep -- 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
