Configure an Environment to Use Multiple Reverse Proxies

When clients are connected to the same CMS UI instance through multiple reverse proxies, the CMS UI needs to know each client’s frontend URL to build correct direct links to the Micro Focus Configuration Manager and Micro Focus Service Manager servers. For example, a client who accesses the CMS UI by reverse proxy https://reverse-proxy-1 should get a direct link by the same https://reverse-proxy-1.

Therefore, a configuration based on relative URLs instead of full URLs should be implemented. When the CMS UI receives a request with a header X-Reverse Proxy, it relates to application URLs as relative URLs and concatenates part of the header with a relative URL. To use this solution the customer should:

1. Configure each reverse proxy in the environment to append header X-Reverse-Proxy with the Reverse Proxy’s frontend URL.
2. Use a relative URL for all servers behind the reverse proxy in the CMS UI configuration.

To perform the actual configuration:

1. Configure reverse proxy to append header X-Reverse-Proxy with the reverse proxy URL for Apache-server. To do this, open file %apache-home-directory%\conf\httpd.conf (where %apache-home-directory% is the Apache server home directory), and add the following lines:

   • LoadModule headers_module modules/mod_headers.so

   • RequestHeader set X-Reverse-Proxy http://srp-server-front-end-url

   Where http://srp-server-front-end-url is the entire reverse proxy’s frontend URL.

2. The CMS UI configuration file should use relative URLs instead of full URLs. For example, instead of http://cm-server/cnc, use /cnc. Specifically, it is very important that the value of tag <ucmdb_ui_url> is defined and uses a relative path.