Important before you start:

• Supported types: .keystore .p12, .pkcs12, and .pfx. We recommend the .pfx format. Check out how to export this type here:
  https://support.globalsign.com/ssl/ssl-certificates-installation/import-and-export-certificate-microsoft-windows
• Ensure the inbound firewall rules have the HTTPS port enabled on the vScope server. Default port is 443.
• The “Key password” and “Keystore password” can be the same in some cases.
• If you don’t have an HTTPS certificate you can read more about how to generate one here:
  https://support.vscope.net/how-to-setup-https-on-vscope-web-server/

You can set up the HTTPS certificate from Settings > Advanced > HTTPS. Simply follow the steps below:

1. Enable HTTPS
2. Upload your keystore.
3. Provide the required information. Depending on the certificate keystore settings, the required fields may vary. In some cases, Key password and Keystore password have the same value.
4. Click Save.
   • If there is something wrong with the settings, an error description is shown next to the Save button. Resolve the errors and click Save again.
   • If the upload was successful “Reload webservice” at the top.
5. Restart the service and give it some time to start up again (approx. 10-15 sec).
6. Any accesses via http://vscope will be redirected to https://vscope. If not:
   • Make sure 443 on the vScope server is not blocked by a firewall!

Note: vScope is behind a reverse proxy.

• vScope is accessed via http://vscope.company.com which forwards traffic to http://vscope

In this case a certificate should not be enabled in vScope but rather in the reverse proxy which then forwards traffic to vScope:

• vScope is accessed via https://vscope.company.com which forwards traffic to http://vscope
  

We do not recommend both https in the reverse proxy and vScope at the same time and that setup is beyond the scope of this guide.

Need help?

Our support team is always happy to be of assistance! Get in touch with them at support@infrasightlabs.com.