03-02-2015 06:24 AM - edited 03-17-2019 04:56 PM
Hello,
we are deploying Jabber 10.6 on a 10.5.2 cluster. XMPP and tomcat certificates are signed by the customer's CA and no certificate warnings for that. But I'm getting warnings for CUCM certificates when Enterprise Trust store is emptied on Windows 7.
I found this when comparing the certificate serialnumber with the ones of the self-signed certificates.
The thing is that I cannot reproduce it everytime.
Does anyone else has a similar behavior ?
When looking at different documents, one might think that CCM certificates also need to be CA signed.
- Jabber 10.6 planning guide (in the Required Certificates for On-Premises Servers section)
- CUCM 10.5.1 Release Notes
Regards,
Jerome
Solved! Go to Solution.
03-02-2015 11:41 AM
Hi Jerome,
Can you check this with jabber client 10.5.x versions.
As there is a BUG reported with jabber 10.6 version where it prompts for certificate errors where as it works fine with jabber version 10.5.
Regards,
Ankoor
03-02-2015 11:41 AM
Hi Jerome,
Can you check this with jabber client 10.5.x versions.
As there is a BUG reported with jabber 10.6 version where it prompts for certificate errors where as it works fine with jabber version 10.5.
Regards,
Ankoor
03-03-2015 07:49 AM
Hello Ankoor,
Jabber 10.5.x works fine, without a certificate warning.
There is a bug for this in the release notes (CSCus64434: Invalid certificate prompt when a CTI Connection is made.)
here is the reason:
Certificate Validation for CTI Connections
Connecting to Cisco Unified Communications Manager using a self-signed certificate results in a certificate validation failure. In this release[10.6], Cisco Jabber uses certificate validation for CTI connections.
Workaround: Sign CUCM certificate or deploy all of them to the workstations
Regards,
Jerome
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide