Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have an issue with a customer's Jabber deployment having ongoing invalid certificate messages. I'm fairly positive it's related to the two domain names they have and some mismatched configurations, but I'm lost on where to start. Here are a bunch o...
No intercluster peers. Been there, done that with the server list. I've replaced IPs with FQDNs in nearly every instance they occur in the environment. No self-signed certs exist for Tomcat on any node in the entire cluster. Ditto for CUP, CUP-XMPP, ...
Nice find.As an update to this issue, I was able to resolve 4 out of 5 certificate warnings in the environment by correcting some things they glossed over on their initial deployment. Primarily: not deploying a "jabber-config.xml" with declared FQDN'...
Noted, thank you. There was never much emphasis placed on deleting old certs and my past experience with them on CUCM has just been for tomcat to stop getting cert warnings on the splash page. Having old self-signed with CA-signed wasn't typically an...
Absolutely.I would also like to note that most of these certs were here before I walked into this situation, I'm here to get things working and clean up! But if I need to clean-up before I can get things working... that's good information to know. Th...
Yes, that is the discrepancy I've observed as well, which is why I'm here for help, haha.My cup, cup-xmpp, and tomcat certs are all CA-signed. However, when I clear my local certs and reset my login, the Jabber client is grabbing a cert that matches ...
