TEC1688585: How do I prevent “No X509TrustManager implementation available” Errors from occurring during the Installation of an OPMS?

Document created by Tom_Wyszomierski Employee on May 26, 2016Last modified by SamCreek on May 26, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC1688585
Last Modified Date:  11/3/2015

Author: Tom_Wyszomierski

  • Products
    • CA App Synthetic Monitor
  • Releases
    • CA App Synthetic Monitor:Release:8.3
  • Components
    • CA APM CLOUD MONITOR (WATCHMOUSE)

 

 

 

    Problem:

     When attempting to install the OPMS, I receive a Java error after entering my ASM API credentials:

     javax.net.ssl.SSLHandshakeException:

     java.security.cert.CertificateException: No X509TrustManager implementation available

 

   Cause:

     This issue typically occurs when the server installed with an On Premise Monitoring Station (OPMS) requires use of an authenticated proxy to access an external

     network. The OPMS installer requires access to https://api.asm.ca.com/1.6/ to register the OPMS being installed. This error may occur during an HTTPS certificate

     exchange, if your server certificate uses an unsupported format as determined by the JVM running the installer.

 

    Workaround:

     This issue can be addressed by disabling certificate validation while running the OPMS installer using the following command:

     ./asm-opms-8.3.0.11.bin -D'$IGNORE_CERTIFICATE$=true'

    Note that the file name of the installer binary will vary slightly if a different version of the OPMS is being installed.

 

 

Search the Entire CA APM Knowledge Base

 

search-kb.jpg

Attachments

    Outcomes