The Jabber app no longer seems to be generating any sort of Kerberos ticket at all. For example, if I connect while on VPN, it does connect without asking for a password but it never creates the kerberos ticket when you run a klist. If I then connect to a file share, I see kerberos tickets are getting generated fine by AFP, SMB, and other services. What should be happening is that after a successful connection of any kerberized SSO service, a kerberos ticket should be generated so that other services now utilize the same TGT (ticket granting ticket). My hunch is that they removed or regressed “kerberization” of the Jabber application for now as a possible workaround until they restore true kerberized SSO functionality?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...