Invalid certificate warning is seen in the Webbrowser after configuring HTTPS on Spotfire server.

book

Article ID: KB0075828

calendar_today

Updated On:

Products Versions
Spotfire Server 7.5 and higher

Description

While using a self signed SSL certificate for configuring HTTPS on Spotfire server, the HTTPS URL might show invalid certificate warning even though the URL is accessible.

image.png

This issue is seen because a self-signed certificate is not considered a trusted certificate by the browser. To consider it as a trusted certificate by the browser, the steps mentioned in the resolution section need to be performed. But before that, ensure the certificate is generated with Subject Alternative Name (SAN) because Modern browsers, such as Chrome, specifically look for the Subject Alternative Name (SAN) extension to validate that the certificate matches the URL you are visiting.

Resolution

In order to resolve the issue, the self-signed certificate must be installed under the Trusted Root Certificate Authorities path. This can be done by using one of the following options, but before that, ensure the self-signed certificate is generated using the following method.

Generate Self-Signed Certificate with Subject Alternative Name (SAN)

  • Modern browsers, such as Chrome, specifically look for the Subject Alternative Name (SAN) extension to validate that the certificate matches the URL you are visiting. Use the -ext (extension) flag to add the SAN directly into your keytool command.
  • Run the following command to generate the key pair:
    • bash keytool -genkeypair -alias gasdspstest07.spotfire.com -keyalg RSA -keysize 2048 -dname "CN=gasdspstest07.spotfire.com" -keypass Test123 -storepass Test123 -keystore C:\spotfire\spotfireserver\14.0.9\tomcat\certs\gasdspstest07.jks -ext "SAN=dns:gasdspstest07.spotfire.com"
    • Explanation of Flags:
      • -ext "SAN=dns:gasdspstest07.spotfire.com"This specifies that an extension field should be added to the keystore.
      • dns:: This prefix is mandatory; it indicates that the following string is a Domain Name

System entry.
Note: If you plan to access the Spotfire server using a short name (e.g., http://gasdspstest07) or an IP address, add those to the SAN as well, separating them with commas as shown below:
bash -ext "SAN=dns:gasdspstest07.spotfire.com,dns:gasdspstest07,ip:10.0.0.1"

 Then follow any of the following options.

Option A: 

1) Open Internet Explorer Browser.
2) Go to Tools==>Internet Options==>Content==>Certificates==>Trusted Root Certification Authorities.
3) Click on "Import".
4) Click on "Browse" and select the certificate that needs to be imported (the one that is used for HTTPS configuration) and click "Next".
5) Check that the "Certificate Store" is set to "Trusted Root Certification Authorities" and click "Next".
6) Click on "Finish".

Option B: 

This can also be done through Microsoft Management Console(MMC) by following the steps below.

1) Open Microsoft Management Console (Start --> Run --> mmc.exe).
2) Choose File --> Add/Remove Snap-in.
3) In the Standalone tab, choose Add.
4) Choose the Certificates snap-in, and click Add.
5) In the wizard, choose the Computer Account, and then choose Local Computer. Press Finish to end the wizard.
6) Close the Add/Remove Snap-in dialog.
7) Navigate to Certificates (Local Computer) and double-click on it.
8) Right-click on "Trusted Root Certification Authorities" and select All Tasks==>Import.
9) Click on "Next".
10) Follow the wizard and provide the certificate file that needs to be imported.
 

Issue/Introduction

This article helps you resolve Invalid certificate warning in the browser after configuring HTTPS on the Spotfire server, when a self-signed certificate is used.