Setting a base url when hosting behind a load balancer acting as proxy

Hello OIM community,

We are using One Identity 9.2 running as containers. We are hosting these containers behind a load balancer, with a different hostname. Our API server, APP server and JOB server are hosted behind this load balancer, with rules like:

  • `/api/*` sends traffic to API server
  • `/app/*` sends traffic to APP server
  • `/job/*` sends traffic to JOB server

Now, the issue with this is, that the servers are hosting their apis on different paths. I.e. the api server hosts its api under just `/*` as far as I'm aware. So far, we have been getting around this by conducting path rewrites on the load balancer, with a regex like `/api/(.*)`. But our CISO office isn't happy with allowing path rewrites on load balancers, and are removing this capability.

How can we manage this in One Identity? My idea was to use the `BASEURL` environment variable for this purpose, but it doesn't seem to do the trick. I configured the variable like:

"BASEURL" = "https://<domain>/api/"

But I get 404s when I request the endpoints from the internet. When I go on the local host, and request the endpoint (`localhost/.../…`), I also get a 404. However, when I request the "standard" endpoint (`http://localhost/…`) I get the expected answers.

So I have a couple of questions for the community. How do you manage a similar set-up? And does the `BASEURL` environment variable even work?