Re: [cas-user] CAS5.3.x: Error getting flow information for URL

2020-02-11 Thread 'Maksim Kopeyka' via CAS Community
Hi Jay, Did you solve problem with Null input buffer? I have the same exception. On Friday, May 18, 2018 at 7:19:07 PM UTC+3, Jay wrote: > > Ray, > To answer your question. > Yes there are two tomcat servers running the application and load balancer > switches between the servers. I will check

Re: [cas-user] CAS5.3.x: Error getting flow information for URL

2018-05-18 Thread Jay
Ray, To answer your question. Yes there are two tomcat servers running the application and load balancer switches between the servers. I will check with the Run team for clustering or setting load balancer to be sticky. Travis, Yes the encryption keys are copied across the servers so they are

Re: [cas-user] CAS5.3.x: Error getting flow information for URL

2018-05-18 Thread Travis Schmidt
Do you have the same webflow encryption keys set in each of the config files on the different servers? If the property is not present the server generates it's own on each server at start up, resulting in each server not understanding the other. On Fri, May 18, 2018 at 8:39 AM Ray Bon

Re: [cas-user] CAS5.3.x: Error getting flow information for URL

2018-05-18 Thread Ray Bon
Jay, Are there multiple CAS servers? Could this be a result of the load balancer switching between CAS servers for each request (load form, post form)? You may need to cluster your tomcats or set load balancer to be sticky. Ray On Thu, 2018-05-17 at 22:42 -0700, Jay wrote: Hi Ray, Yes, it

Re: [cas-user] CAS5.3.x: Error getting flow information for URL

2018-05-17 Thread Jay
Hi Ray, Yes, it does not allow the user to be validated and login successfully. It redirects back to login page only. Any suggestion to look into specifically. We see this issue when we hit the load balance url but not when we directly access the server url. Thanks, Jay On Thursday, May

[cas-user] CAS5.3.x: Error getting flow information for URL

2018-05-17 Thread Jay
Hello everyone, We have CAS application running in Tomcat in two different instances and load balanced by a F5 url. Any application is configured with the F5 url for login authentication and authorization. We have customized the url to *https:///las/v3/login* (Naming the war file as