What must you do to fix the TLS login error stating that the security certificate is not installed?

What must you do to fix the TLS login error stating that the security certificate is not installed?

• A. Install the SM Identity certificate into the Trusted Root Certificate Authorities on CM
• B. Install the Certificate Authority certificate that signed Avaya Aura Session Manager's Identity certificate into the Trusted Root Certificate Authorities on the PC
• C. Import the Identity Certificate from the Security menu of the one-X Communicator
• D. Export the identity certificate from Avaya Aura Session Manager and import it into the PC using copy and paste

Answer: (B)

The correct answer is to install the Certificate Authority certificate that signed Avaya Aura Session Manager's Identity certificate into the Trusted Root Certificate Authorities on the PC. This action is necessary because the security certificate presented by Avaya Aura Session Manager must be trusted by the client in order to successfully establish a secure TLS connection. When the client, such as a PC running one-X Communicator, does not recognize or trust the certificate presented by Session Manager, it results in a login error. The root cause of this error typically stems from the absence of the proper Certificate Authority (CA) certificate in the client's trusted certificate store. By installing the CA certificate that signed the Session Manager's Identity certificate into the Trusted Root Certificate Authorities store on the PC, the client recognizes the certificate as valid, thus allowing a secure connection without errors. In contrast, other actions, such as installing the SM Identity certificate directly into CM, importing the Identity Certificate from the Security menu of the one-X Communicator, or exporting and importing the identity certificate manually, do not address the core issue of establishing trust for the certificate chain. Without the root certificate from the Certificate Authority, the client will still fail to authenticate the session securely. Therefore, ensuring that the CA certificate is trusted is the fundamental step to

The correct answer is to install the Certificate Authority certificate that signed Avaya Aura Session Manager's Identity certificate into the Trusted Root Certificate Authorities on the PC. This action is necessary because the security certificate presented by Avaya Aura Session Manager must be trusted by the client in order to successfully establish a secure TLS connection.

When the client, such as a PC running one-X Communicator, does not recognize or trust the certificate presented by Session Manager, it results in a login error. The root cause of this error typically stems from the absence of the proper Certificate Authority (CA) certificate in the client's trusted certificate store. By installing the CA certificate that signed the Session Manager's Identity certificate into the Trusted Root Certificate Authorities store on the PC, the client recognizes the certificate as valid, thus allowing a secure connection without errors.

In contrast, other actions, such as installing the SM Identity certificate directly into CM, importing the Identity Certificate from the Security menu of the one-X Communicator, or exporting and importing the identity certificate manually, do not address the core issue of establishing trust for the certificate chain. Without the root certificate from the Certificate Authority, the client will still fail to authenticate the session securely. Therefore, ensuring that the CA certificate is trusted is the fundamental step to