After configuring SSL on Strategy Web & Library, when the end user clicks on the Library icon in Strategy Web, the HTTP call switches to a non secured protocol (http instead of https) and a network error message can appear, depending on the network configuration.
STEPS TO REPRODUCE :
1. Login to Strategy Web.
2. Click on the Library icon in the main menu: the login page should be launched. Note that, at this step, the SSL protocol is not active any more. As a consequence, the URL will change into a non http URL and can cause the following error message:
The site can't be reached
CAUSE
This configuration requires additional settings in the Tomcat (or any JSP-based) web server by design, as explained here.
When the end user accesses https://mycompany.Strategy.com/MicroStrategyLibrary/app
the redirection can be done to an authentication page that is not secured. Since the load balancer forwards requests to the Web server (Tomcat with the default installation) on port 8080 using HTTP and not HTTPS, Tomcat is not aware of the scheme by that needs to be used in this case.
ACTION
We need to make the Tomcat connector aware that end users actually access Tomcat through HTTPS. To do so, the HTTP connector needs to be updated in Tomcat's server.xml file using the Proxy Support documentation, below is a sample on how to accomplish this:
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" secure="true" proxyPort="443" scheme="https" />
