Hi,
I'm configuring a lab deployment for Jabber for Windows using SSO Kerberos for an upcoming deployment - 2 x UCM, 2 x IMP, 1 x CUC on 11.5. Have deployed ADFS and CA in lab. UCM has Tomcat and CallManager certifcates signed by CA, IMP has cup-xmpp signed by CA, CUC also has Tomcat signed by CA. UCM and IMP certs are using the Multisan certs. All is working as expected - user logs onto Windows 10 laptop.....Jabber autostarts and auto logs in via SSO - happy days
The only issue is I am getting one (1) certificate warning which is the Multisan Tomcat certificate which doesn't make sense to me as when I view it is shows me the certifcate is OK and the Root is trusted.......all the server names are fully resolvable and this is proved by the fact that you usually get several certificate warnings from UC, IMP and CUC.
Has anyone seen something like this? I put in a screenshot of the certifiate when viewed from user PC
TIA
