Cisco Bug: CSCut42571 - Invalid certificate prompt when softphone registration is made.
Sep 15, 2015
- Cisco Jabber for Windows
Known Affected Releases
Symptom: During Jabber SOFTPHONE registration to CUCM, response is providing Cisco CallManager leaf certificate to the Jabber Client. However if the leaf cert has been signed by an Intermediate CA, then the response should provide all intermediate CA certs to the Jabber client to allow the client to build a valid certificate chain to a trusted Root. Conditions: Steps to Reproduce : ================== - Set up a Root CA Authority : "CA-Root1" - Set up an intermediate CA Authority : "CA-Int1" - Sign the CallManager certificate using "CA-Int1" - On a Windows Desktop, deploy the "CA-Root1" certificate as a Trusted Root Certificate Authority in the Windows Cert Store - Run Jabber 10.6, Sign In and use Softphone mode Expected Result : =============== - Sofphone registration is made without any Invalid Certificate Prompt on Jabber Actual Result : =============== - An Invalid Certificate prompt will be display for the CallManager Certificate when SOFTPHONE registration is made
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases