Planning Guide for Cisco Jabber 14.1 - Security and certificates

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_1/cjab_b_planning-guide-for-jabber141/cjab_m_planning-security-and-certificates-129.html

Published

2024-04-02

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

Cisco copyright; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Jabber on Android 7.0 and later recognizes only CA-signed certificates. in context
• If a user accepts an untrusted certificate, Jabber connects and saves the certificate. If the user declines it, the connection to that service fails. in context
• Cisco advises using an FQDN, not an IP address or bare hostname, for each service in the Unified CM service profile, because public CAs generally require an FQDN as the server identity. in context
• When services present self-signed certificates, Jabber users are always prompted to accept or decline them. With administrator-deployed CA-signed certificates, users are not prompted. in context
• The servers that present certificates to Jabber include Unified CM (HTTP/Tomcat and CallManager), IM and Presence (HTTP/Tomcat and XMPP), Unity Connection (HTTP/Tomcat), and Expressway-E (one server certificate for HTTP, XMPP and SIP). in context

Cite this source record

APA

WarmTransfer. (2024, April 2). Planning Guide for Cisco Jabber 14.1 - Security and certificates. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-jabber-141-planning-security-certificates

BibTeX

@misc{warmtransfer-cisco-jabber-141-planning-security-certificates,
  title  = {Planning Guide for Cisco Jabber 14.1 - Security and certificates},
  author = {{WarmTransfer}},
  year   = {2024},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-jabber-141-planning-security-certificates},
  note   = {Cisco Systems, accessed 2026-09-25}
}