Setting up OAM WebGate behind a Load Balancer that does context based routing

Setting up a OAM webgate behind a load balancer could pose routing issue. For example, if there is a load balancer doing a context based routing as below:

http://<hostname>:<port>/protect mapped to the backend web server http://<webserver>:<port>/protect

The problem starts when traffic is intercepted by webgate, OAM authentication is successful and OAM tries to set the cookie information to web server using the url that looks like:

http://<hostname>:<port>/obrar.cgi......

This url will not make to the backend web server because there is no context to route this traffic. The traffic dies at the load balancer and an error message is displayed in the browser.

To resolve, create a new context on the load balancer that will send the return traffic from OAM server to web server.

http://<hostname>:<port>/obrar.cgi  map to http://<webserver>:<port>/obrar.cgi

Access the webserver now, after authentication, it will take to the resource successfully.

Have fun…