Now that web reports supports AD logins, we would like to configure HTTPS for web reports. The user guide tells you how to use open ssl to create a request, self-signed and install a certificate. What if I want to use a certificate generated from our Windows Certificate Authority? I was issued a certificate (pfx) from our Certificate Authority, but how do I install it? Has anyone done this before? Surely there must be a better way of setting up SSL?
Maybe someone else will find this useful. I took the certificate generated from the certificate authority and converted it to PEM format (.cer).
openssl.exe pkcs12 -in e:\certs\bigfix.pfx -out e:\certs\bigfix.cer -nodes Enter Import Password: ******* MAC verified OK
Then I used the bigfix.cer file and followed the directions for setting the
_WebReports_HTTPServer_UseSSLFlag
,
_WebReports_HTTPServer_SSLCertificateFilePath
, and
_WebReportsHTTPServer_PortNumber
client settings. And updated the entry in the AGGREGATEDBY table of the BFEnterprise SQL database to point to the new URL. Wasn’t exactly straight forward, but it works in the end.
Feature requests:
Add an option in the BesAdmin tool to setup SSL
Option to redirect HTTP (port 80) to HTTPS (port 443). One option is to setup IIS to listen on port 80, but I would rather not waste resources on such a small feature.