AwE-5103 Network Socket Error PKIX path validation failed signature check failed - Applications Manager

Products

• Automic Applications Manager

Issue/Introduction

This article provides steps to resolve the AwE-5103 network socket error occurring during the AppWorx Java Client login process. This error typically presents as the following Java exception: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed.

Symptoms

• Error details also show error "java.security.SignatureException: Signature does not match."

Environment

Applications Manager 

Cause

The "signature check failed" / "Signature does not match" error often indicates that the user_keystore and user_keystore_config files on the client machine are outdated, corrupted, or do not match the Master's data directory files. This mismatch causes the SSL handshake to fail, as the client cannot validate the server's certificate.

Resolution

Troubleshooting:

To verify if the user_keystore is corrupted or mismatched, run the following command on both the Master and the Client keystore files:

keytool -list -v -keystore /path/to/user_keystore

1. On the Master: The command should return the certificate information.
2. On the Client: If the keystore is corrupted or mismatched, you may receive an "invalid password" error or an inability to read the certificate information.

Resolution:

To resolve this issue, synchronize the keystore files from the Master to the Client:

1. Navigate to the client-side configuration directory (e.g., C:\Users\[username]\AppWorx\[mastername]).
2. Delete the existing user_keystore and user_keystore_config files.
3. Navigate to the Master server's data directory (e.g., $AW_HOME/data).
4. Copy a fresh set of user_keystore and user_keystore_config files from the Master directory.
5. Paste these files into the client-side directory identified in step 1.
6. Restart the AppWorx Java Client.

Additional Information

• To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.
• To subscribe to status updates on this issue, please see How to subscribe to a KB article.