02-23-2015 07:33 AM - edited 03-17-2019 04:55 PM
Hello,
we noticed an issue upgrading jabber for windows clients from 10.5 to 10.6
after upgrade on some PC's the jabber is unable to start and it outputs a message: invalid certificate,...
The strange thing is that is non happening on all the PC's but only in some.
we are not using signed certificates, but the self-signed auto generated from cucm/im servers
Any idea?
Giovanni
02-23-2015 02:29 PM
Hi Giovanni Sciotti,
a) all the PC's have the same OS (for example: Windows 7, with the same patch)?
b) when you remove and install version 10.6 again, are you able to start Jabber?
c) you did a manual upgrading or an automatic one?
Regards.
02-23-2015 02:35 PM
Hello!
A) yes, same os windows 7
B) no also uninstalling and installing jabber 10.6 the same issue occours. I need to uninstall and install 10.5 to get jabber working again
C) automatic. In our network we deployed jabber upgrade with automatic mode.
sone client upgraded fine. Some no! :(
02-24-2015 10:38 AM
Hi Giovanni Sciotti,
ok.
Could you please print the error message?
Also, double check if there is any difference in the Windows7 Security patch between one PC (that the upgrade was ok) and the other PC (where the upgrade was not ok).
Regards.
02-25-2015 07:52 AM
Ok, the error images are (but in italian) in attach.
Jabber says that the certificate is not valid :S
And that is not a root CA acceptable, but we are using self signed certificates
PC's should be identical (same model and all with same software) :(
Regards
Giovanni
02-25-2015 09:08 PM
Ok, no prob to be in italian.
In 'Internet Explorer' (for example) > Tools > Internet Options, check the Security, Content and Advanced tab for any differences.
Ex.: in the Advanced tab > Security section
Regards.
03-09-2015 07:14 AM
Hello,
there are no differences between 2 PC's :(
Giovanni
03-09-2015 07:39 AM
Hello,
i found the solution.
The problem is on the PC's that have the FIPS enabled.
To disable you can follow this step by step Guide:
http://docs.trendmicro.com/all/ent/sc/v3.0/en-US/cmcolh/t_fips.html
Regards.
Giovanni
03-09-2015 12:16 PM
02-25-2015 09:25 PM
You're going to have those certs signed (Tomcat) by either an internal CA or public CA as Jabber will use https request.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide