Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Problem

When running any of the SeaLights agents, you may come across an error related to PKIx/SSL libraries. For example:

javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake …
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed …

Cause

These errors could point to an issue with creating a secure connection to our server due to a misconfigured or missing certificate. The missing certificate is often the Selaights Security certificate, sometimes your Corporate certificate.

The instructions below detail the steps required to add the SeaLights certificate to your local Java Keystore.

Solution

  1. Retrieve the SeaLights certificate from your dashboard:

  • While logged in, click the “Lock” icon to the left of your address bar.

  • Export the certificate to your local machine:

On Windows: In the Details tab, click on Copy to File and ensure the exported certificate is in .cer/.der format

On Mac: Dragging the certificate icon to your desktop will export it

Make sure the certificate you’re downloading is issued by Amazon Web services. In some organizations, the firewall modifies/replaces the certificate and leds to continue facing the connectivity issue because the certificate will be marked as invalid. In this case, please contact Sealights Support to get a copy via email for example.

2. Add the certificate to the Java Keystore:

keytool -importcert -alias your-alias -keystore cacerts.jks -file certificate.pem -storepass password

 

(Optional) Convert the .cer certificate file to .pem format:

  • In some cases, it may be necessary to convert the exported certificate to PEM format to be loaded into the JKS (Java Key Store). To do so, use the following command:

openssl x509 -inform der -in certificate.cer -out certificate.pem

The SeaLights certificate should be added to any Java keystore that communicates with SeaLights.

3. Validate the certificate was imported into the keystore file being used by the JVM with the following command:

Workaround

You can disable the cert check (not a long-term solution):

sl.ignoreCertificateErrors=true

Helper

Here's a Bash script that uses the keytool command to check the expiration dates of certificates in a Java keystore and notifies you about certificates that are either expired or will expire in less than 30 days:

Bash

PowerShell

#!/bin/bash

# Path to your Java keystore
KEYSTORE_PATH="/path/to/your/keystore.jks"
# Keystore password
KEYSTORE_PASSWORD="your_keystore_password"

# Number of days for expiration threshold
EXPIRATION_THRESHOLD=30

# Get current date in epoch format
CURRENT_DATE=$(date +%s)

# Loop through each entry in the keystore
while IFS=' ' read -r alias; do
    # Get certificate expiration date
    expiration_date=$(keytool -list -v -keystore "$KEYSTORE_PATH" -storepass "$KEYSTORE_PASSWORD" -alias "$alias" | grep Valid | awk -F ',' '{print $2}' | sed 's/^[ \t]*//')

    # Convert expiration date to epoch format
    expiration_epoch=$(date -d "$expiration_date" +%s)

    # Calculate days until expiration
    days_until_expiration=$(( (expiration_epoch - CURRENT_DATE) / 86400 ))

    if (( days_until_expiration <= 0 )); then
        echo "Certificate '$alias' has already expired!"
    elif (( days_until_expiration <= EXPIRATION_THRESHOLD )); then
        echo "Certificate '$alias' will expire in $days_until_expiration days."
    fi
done < <(keytool -list -keystore "$KEYSTORE_PATH" -storepass "$KEYSTORE_PASSWORD" | grep "Alias name:" | awk -F ': ' '{print $2}')

exit 0
# Path to your Java keystore
$KeyStorePath = "C:\path\to\your\keystore.jks"

# Keystore password
$KeyStorePassword = "your_keystore_password"

# Number of days for expiration threshold
$ExpirationThreshold = 30

# Get the current date
$CurrentDate = Get-Date

# Load the keystore
$Keystore = [Security.Cryptography.X509Certificates.X509Certificate2Collection]::new()
$Keystore.Import($KeyStorePath, $KeyStorePassword, [Security.Cryptography.X509Certificates.X509KeyStorageFlags]::DefaultKeySet)

# Loop through each certificate in the keystore
foreach ($cert in $Keystore) {
    $expirationDate = $cert.NotAfter

    # Calculate days until expiration
    $daysUntilExpiration = ($expirationDate - $CurrentDate).Days

    if ($expirationDate -lt $CurrentDate) {
        Write-Host "Certificate '$($cert.Subject)' has already expired!"
    }
    elseif ($daysUntilExpiration -le $ExpirationThreshold) {
        Write-Host "Certificate '$($cert.Subject)' will expire in $daysUntilExpiration days."
    }
}

$Keystore.Dispose()

Replace /path/to/your/keystore.jks with the actual path to your Java keystore file and your_keystore_password with your keystore password. Set appropriate permissions on the script file and execute it in a proper environment.
Please note that this script assumes that the keytool command is available in your environment (usually comes with Java installations). Also, ensure that you have the necessary permissions to access the keystore file.

  • No labels