cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1542
Views
0
Helpful
2
Replies

Jabber 10.6 presenting CUCM certificate

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)

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/planning-guide/CJAB_BK_CD3376A0_00_cisco-jabber-106-planning-guide/CJAB_BK_CD3376A0_00_cisco-jabber-planning-guide_chapter_0110.html

- CUCM 10.5.1 Release Notes

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_5_1/CUCM_BK_CE15D2A0_00_cucm-release-notes-1051/CUCM_BK_CE15D2A0_00_cucm-release-notes-1051_chapter_01.html#CUCM_RF_BDB72D3A_00

 

 

Regards,

Jerome

1 Accepted Solution

Accepted Solutions

Ankoor Bek
Cisco Employee
Cisco Employee

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

View solution in original post

2 Replies 2

Ankoor Bek
Cisco Employee
Cisco Employee

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

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