Skip to Content
Information
This documentation supports the 9.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.Click here to view the documentation for a supported version of Remedy Single Sign-On.

Example of a client not responding with a certificate

The following log from the Transport Layer Security (TLS) debug logs shows an example of when the client does not respond with a certificate. In this example, there is a lack of logging between *** Certificate chain and the *** section terminator.


*** ServerHelloDone
http-8443-1, WRITE: TLSv1 Handshake, length = 1606
http-8443-1, READ: TLSv1 Handshake, length = 109
*** Certificate chain
***
http-8443-1, SEND TLSv1 ALERT:  fatal, description = bad_certificate
http-8443-1, WRITE: TLSv1 Alert, length = 2
http-8443-1, called closeSocket()
http-8443-1, handling exception: javax.net.ssl.SSLHandshakeException: null cert chain

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Atrium Single Sign-On 9.0