WebUI SSL Instructions

After enabling the WebUI, I looked at the admin guide for implementing an SSL certificate. The guide is fairly sparse on getting a certificate generated so I’m wondering if I need to have a certificate that has a password or not. The WebReports requires that no password is on the key file but the SCA certificate requires a password. Can we get some clarification?


To that point, I am also seeing my core server listening on 52315 and when I navigate to it, it asks for my PIV card password. I’m assuming this is a piece for SSO. I’m also assuming that when I secure the WebUI in the fashion that the Admin guide states, that port will be secured as well?

Let me double check in the morning. My memory suggests to me our cert doesn’t have a password associated with it.

Port 52315 is an internal port that the WebUI uses made available by the platform. You can completely disable outside access for port 52315. I think if you follow the instructions on the administrator guide, it only secures 80/443 (or whatever port you’ve pointed the WebUI at). Right now I think 52315 is a self signed cert.

If you’re wondering what’s up with port 52315, it serves a lot of routes that get consumed by our ETL process to populate webui.db (basically a cached version of BFEnterprise data).

I don’t mind it being there but I know that our vulnerability scans will complain that there is no signed certificate attached. I’m just trying to be ahead of the curve.

1 Like

I am having the same issue. Can we get more specific instructions on how to properly generate and install this cert.

I just went back and confirmed that you don’t need a password for your SSL certificate for the WebUI.

Okay but it looks like we still don’t have solid instructions on how to replace it with a signed cert?

Did you get anywhere with this ?.. I have a .CRT generated but Im having a devil of a job getting a valid .key to be recognised…

I have the .crt in place, With the .key file. I cannot connect and a netstat -an shows a syn_sent on port 8081 (which is the port I chose for the WebUi… If I remove the .key file. I can connect but I have to allow a site security exception in the browser.

Used OPENSSL to generate .KEY and .CSR with 2048 RSA encoding
Using Enterprise Certificate Authority, am able to use the .CSR from OPENSSL to create .CER
There is NO WAY within Microsoft Certificate authority to export this certificate in any other format other than .CER
The available options for exporting a cert within Certificate Authority (OR) from MMC add Certificate to local computer then “IMPORT” the certificate generated by Certificate Authority and export into x509 (DER or Base 64 or P7B) all of these can only be saved as .CER ****we need a .CRT
once you have the cert then OPENSSL to the rescue.

Open command prompt and browse to a directory to save all these files. Install OPENSSL x64 binaries and ensure to add openssl.exe to the [PATH] variable.

Create ssl.conf with required fields filled out (change as needed under [ req_distinguished_name ]

[ req ]
default_bits = 2048
default_keyfile = keyfile.pem
distinguished_name = req_distinguished_name
attributes = req_attributes
prompt = no
output_password = bigfix

[ req_distinguished_name ]
C = US
ST = Virginia
L = McLean
O = Information Technology LAB
OU = Lab
CN = BigFix
emailAddress = admin@MyDomain.com

[ req_attributes ]
challengePassword = bigfix

Ensure to add all the aliases which will be used for all things BigFix in the following format, give this to be used along with the creation of the Cert from CA (change MyDomain.COM to the domain where BigFix will be installed)

send ssl.csr to CA to get ssl.cer
BigFix WEBUI needs this specific name “ssl.crt and ssl.pvk” for the ssl to work
make copy of ssl.key and rename to ssl.pvk
make copy of ssl.cer and rename to ssl.crt
stop besrootserver service on BigFix root server
copy ssl.crt and ssl.pvk to "\Program Files (x86)\BigFix Enterprise\BES Server\WebUI"
start besrootserver service on BigFix root server
open browser and type in link to https://bigfix for accessing WEBUI

1024 and 2048 refer the RSA strength. Where is the issue arising? Did you combine the cert and the certs of your CA and SCAs (if applicable)? Your instructions don’t seem to include that step but your RCA and applicable SCA certs needs to be combined into one certificate.

Got it to work: -

openssl req -new -newkey rsa:2048 -nodes -out ssl.csr -keyout ssl.key -subj “/C=US/ST=Virginia/L=McLean/O=CDM/OU=Information Technology/CN=BigFix”
saved 2 files ssl.csr and ssl.key
send ssl.csr to CA to get ssl.cer
make copy of ssl.key and rename to ssl.pvk
make copy of ssl.cer and rename to ssl.crt
stop besrootserver service on BigFix root server
copy ssl.crt and ssl.pvk to "\Program Files (x86)\BigFix Enterprise\BES Server\WebUI"
start besrootserver service on BigFix root server
open browser and type in link to https://bigfix for accessing WEBUI
** if your cert is issued from enterprise CA you are able to add DNS names to aliases being used to access the WEBUI: - common examples of accessing the web link are as follows
NOTE* while requesting this cert make request to add subject alternate names (DNS) names to this cert by adding this to the “Additional Attributes:” section of the cert generating process
**this is so any of the names listed here can be used in the web browser to resolve as a valid cert.

Hello guys… I hope someone can answer this old post:
I am kind of confuse on this matter… I am using webui in a different server. And from the certs folder there is already the files auth_cert.crt, auth_key.key and ca.crt.
If I moved them out of the certs folder and include my certs ssl.crt and ssl.pvk the webui service doesn’t start.
If I keep them and also included my certs, the webui page doesn’t consider them and refers to the default certs:

The certificate is not trusted because it is self-signed. The certificate is only valid for localhost

Any extra advise?

That’s how I have it. You’re best of reading this post.


For your ssl.conf file, the format for adding the aliases is not clear. Would you please clarify?

Is port 52315 opened as initiating from the root server to the remote webUI server? I cannot have a port opened bi-directionally.