Integration Adapter for Smarts Manager is not connecting to NCM DS API, even with correct credentials

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Smarts NCM Integration Adapter for Smarts Manager cannot connect to NCM DS API.

The following conditions, events or system behaviors may be observed with this issue:

• Test failed is reported when attempting to connect to the Smarts NCM DS API, even when correct sysadmin credentials are used.
• Error seen in Smarts NCM Integration Adapter for Smarts Manager logs:

ERROR  Public API Connection is DOWN.  (com.voyence.integration.smarts.util.VoyenceConnectionBroker)
javax.naming.NamingException: Failed to retrieve Naming interface for provider https://<ServerName>:8880/invoker/JNDIFactory [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]

 

Environment

VMware Smart Assurance - NCM

Cause

Normally, this error is caused by incorrectly imported self-signed certificates.

Resolution

If you encounter this issue, do the following:

1. Run the following commands to export the current certificate:

source /etc/voyence.conf

$JAVA_HOME/bin/keytool -export -keystore $VOYENCE_HOME/jboss/server/vc-server/deploy/1vc.sar/voyence-ssl.keystore -alias selfsigned -file cacert

2. At prompt, press <Enter> without entering a password.
3. Run the following command to re-import the certificate:

$JAVA_HOME/bin/keytool -keystore $JAVA_HOME/jre/lib/security/cacerts -import -alias selfsigned1 -file ./cacert

4. Run the following commands to restart Smarts NCM integration adapter service:

service ncmsmartsadapter stop
service ncmsmartsadapter start