"Received fatal alert: certificate_unknown" errors after upgrading TrueSight Orchestration to version 8.2

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Atrium Orchestrator Platform


    COMPONENT:

    BMC Atrium Orchestrator Platform


    APPLIES TO:

    TrueSight Orchestration Platform 8.2



    PROBLEM:

    After I upgrade TrueSight Orchestration to version 8.2, I see errors in my log files:

    01 Jan 2019 01:01:01,001 [Thread=ActiveMQ Task-1] WARN DiscoveryNetworkConnector Could not start network bridge between: vm://ao-grid-framework-embedded-broker-586bdfd4-641a-4290-a382-123456789ABC and: ssl://12.34.56.78:28090 due to: java.security.cert.CertificateException: No subject alternative names present 
    01 Jan 2019 01:01:01,001 [Thread=ActiveMQ BrokerService[ao-grid-framework-embedded-broker-586bdfd4-641a-4290-a382-123456789ABC] Task-90] ERROR TransportConnector Could not accept connection from tcp://12.34.56.78:28090 : javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown 


    The IP addresses in the errors are the servers with my TSO peers, and the ports in the errors are the ports I configured for embedded instances of Remedy Single Sign-On (RSSO) (28090 and 38090 by default). After the upgrade, my instances of RSSO do not synchronize user or group information as they did before the upgrade.


    CAUSE:

    Due to a defect, RSSO returns a handshake error when it tries to connect securely to other instances of RSSO to exchange user and group information.


    SOLUTION:

    BMC is targeting a solution for a future release. If you need a solution in your current version, please contact BMC Customer Support.


    Article Number:

    000168950


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles