Configuring Quality Management Suite client to run behind a reverse proxy providing SSL termination (Optional)

It may be desirable to run the QMS client web application behind a reverse proxy that provides SSL termination services to improve performance, scalability, or simplify infrastructure management. The web client services http requests on the port bound to the website in IIS, reporting requests on port 8031 and live audio monitoring requests on port 4533. The base URLs for reporting and live audio monitoring are determined at runtime from the QMS client configuration specific to using SSL. Running behind a proxy providing SSL termination SSL is turned off in the backend application host so the reporting and live monitor URLs will be http based. This causes a mixed content condition in most browsers because the original client URL is https based with the SSL termination occurring at the proxy, but reporting and live monitor URLs will be rendered as http to agree with the QMS client SSL setup. In addition to any administration at the reverse proxy setting ForceHostSchemeToHttps in the web.config will resolve this issue. Complete the following steps:

1. Open the web.config file for editing (found in the QMS Client IIS directory, which is normally C:\Inetpub\wwwroot\QMS\Web.Config)
   

2. Add a key value pair in the appSettings scope with keyname ForceHostSchemeToHttps and value true. The IIS pool will need to be recycled to pickup this change.

3. Add treatments at the reverse proxy for the three ports the QMS web application services http traffic on. Secure requests starting with path /QMS are treated by the IIS bound endpoint at the backend, requests starting with /api/reports are treated by port 8031 at the backend and any secure request to 4533 is relayed to 4533 at the backend.