When you attempt to login an Avaya Workplace client using TLS, it fails and displays the error: Phone service problem: The server certificate is not trusted. Which action would you take to resolve…

Question

Options

• AImport the Identity Certificate from the Security menu of the Workplace client into the Avaya Aura
• BInstall the Certificate Authority certificate that signed the Avaya Aura Session Manager (SM)
• CExport the identity certificate from Avaya Aura Session Manager (SM) and import it into the PC
• DInstall the Avaya Aura Session Manager (SM) Identity certificate into the Trusted Root Certificate

• A
  5% (2)
• B
  74% (29)
• C
  13% (5)
• D
  8% (3)

Explanation

When a TLS connection fails with "server certificate is not trusted," the client doesn't recognize the Certificate Authority (CA) that vouched for the server's identity - installing the CA certificate (option B) into the client machine's trusted store teaches the OS/client to trust any certificate signed by that CA, which resolves the error at the root cause.

Why the distractors are wrong:

• A is backwards - identity certificates prove your identity to a server; importing one from Workplace into Aura doesn't fix a trust problem on the client side.
• C is a common temptation but wrong: exporting the SM's identity certificate and importing it directly into the PC bypasses the proper CA trust chain and is not how PKI is meant to work; you trust the signer (CA), not every individual leaf certificate.
• D is close but subtly wrong - installing the SM's identity certificate (not the CA certificate) into Trusted Root would be non-standard and fragile; it only trusts that one cert rather than the entire CA chain.

Memory tip: Think "trust the signer, not the signed." When a client says a certificate isn't trusted, it doesn't know who vouched for it - so you install the CA (the voucher), not the server's own certificate.

No community discussion yet for this question.