We have two web app with same security-domain
Big-IP set mapping mysite.com to 10.10.1.113
User browses http://mysite.com/gateway/index.jsp
10.10.1.113/gateway/index.jsp received request OK, then we did
But web app "dealing" will popup login page, seems authenticated data lost...
If we don't use Big-IP
2. requet.login then repose.redireect to http://10.10.1.113/dealing/
3. http://10.10.1.113/dealing/ will display home page just like user logined
How to config Big-IP to redirect authenticated request ?
You should verify whether the application is setting session cookies that have (or don't have) the domain or path parameters set. If these don't match the various paths and domain correctly then the session doesn't "redirect". You should be able to track this using the network inspector in the browser's dev tools and then compare against the app's configuration.
Thanks for your reply.
Our app server is JBOSS EAP 7, and we also enable SSO in the server, so if user request
and login, then redirect to
we don't need to login again and we could found cooke named JSESSIONIDSSO.
But if we change ip "10.10.1.113" of url to domain name "mysite.com" and setup mapping in Big-IP,
seems JSESSIONIDSSO did not redirect to http://mysite.com/dealing/
we could not find cookie JSESSIONIDSSO in the browser dev tool and http://mysite.com/dealing/ popup login page.
How to setup rule of Big-IP to redirect JSESSIONIDSSO ?
It might be a good idea to open a case with Red Hat to get some support in configuring the system to do SSO with a load balancer involved.