02-08-2013 01:34 AM
I am wrestling with a quick report problem in our environment.
We are using SSL and port 443 to get access to our Sitescopeserver (Linux CentOS).
Our webaccess is through a very locked down firewall and we had a struggle to get access through port 443 at all.
The GUI is working fine, however the Quick Reports are not working...
This seems to be because the reports are using port 8888 by default and this port is of course blocked by the firewall.
Now, I would like to configure the quick reports to go through the same SSL port as we use for the GUI, but this does not seem to be possible?
Can someone confirm that my understanding is correct? Do I need to setup a second SSL port and redirect the QR through this port?
If it is not possible to use the same SSL port as the GUI, do someone have an up to date guide how to get the certificates to work for this new port? The Tomcat server.xml file that is used for the GUI does not seem to have any impact on the QR port settings and the documentation in the deployment guide points to a non existing document (\docs\HTTPSaccess.htm).
02-11-2013 07:39 AM
I have tried and failed to do what you are attempting. I believe the GUI and Reporting must be on seperate ports. I ended up configuring HTTPs on port 8888. Of course I had to fight to get that allowed through the firewall. If anyone else has been successsful configuring SiS to use a singel port (443) I would also be interested in knowing the solution.
02-11-2013 08:00 AM
Thanks for replying.
I have experimented with setting the "Classic user interface secure port" (with the config_tool.sh) to 443
but this does not work.
As I recall it, I ended up with a certificate error, no matter how I tried.
I think that the classic interface does not use the same mechanism as the GUI to handle the certificates.
Lets hope that some friendly soul tells us what can be done and how.
02-11-2013 01:33 PM
GUI and reports should run on different ports. To set SSL for reports you need to update next entries in master.config:
_httpsActivePort=<new Port for secure connections, different from the new UI secure port set on the conf.xml)
_httpSecureKeyPassword=password (sitescope will encrypt the password upon restart)
_httpSecureKeystorePassword=password (sitescope will encrypt the password upon restart, usually same as above)
_httpSecurePort=<new Port for secure connections, different from the new UI secure port set on the conf.xml, same as above)
The passwords are the ones you used to create keystore and cert for SSL GUI. You can type them as plain text and SiS will encrypt them in next restart (Oliw that's the step you're missing)
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you haven’t tried it yet, come and join us in our entitled forums at Support Customer Forums