I’ve heard from my help desk that they had a few users report the prompt for accepting a cert. Unfortunately, they gathered zero details for me and just had the users accept the cert…
Good to know it’s not just us though. From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Jason Aarons Sent: Thursday, November 11, 2021 10:17 AM To: Gary Parker <g.j.par...@lboro.ac.uk> Cc: cisco-voip@puck.nether.net Subject: [External] Re: [cisco-voip] Jabber Users Prompted To Accept Webex Cert Webex clients update switched from the Quovadis Root CA which was older and being retired, to the IdenTrust Root CA which it dates back to 2014. The IdenTrust Root CA certificate is contained within the default trust store of all major operating systems by default. Not clear why IdenTrust is missing on your computers. Guessing maybe you disabled automatic root updates at some point or don’t have Windows updates running ? https://serverfault.com/questions/752146/why-are-many-admins-using-turn-off-automatic-root-certificates-update-policy Cisco Field Notice we didn’t notice https://www.cisco.com/c/en/us/support/docs/field-notices/721/fn72120.html On Thu, Nov 11, 2021 at 6:22 AM Gary Parker <g.j.par...@lboro.ac.uk<mailto:g.j.par...@lboro.ac.uk>> wrote: Morning all, a few years back we had a problem where lots of our managed Windows service users were complaining that their Jabber clients had started rejecting a certificate offered by idbroker.webex.com<http://idbroker.webex.com> This thread on community.cisco.com<http://community.cisco.com> (https://community.cisco.com/t5/unified-communications/jabber-idbroker-webex-com-certificate-request-during-the-first/td-p/3216376) showed we weren’t the only ones, but that it seemed limited to managed clients. We solved this by adding the EXCLUDED_SERVICES=WEBEX flag to the installer on our managed clients. Fast forward to today and we suddenly have a load of service desk cases from users again. Nothing has changed in our configuration of Jabber client, IM&P servers or expressways. The clients haven’t been updated recently, and this time we’re also seeing the “Certificate not valid” pop-up on unmanaged Windows machines as well as our managed service. The cert that’s being rejected has validity start date of late September, so it doesn’t appear to be a cert that’s only just been brought into use. Is anyone else seeing this today? As a workaround I’ve added: <ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices> ...to our jabber-config.xml, but that will require users to manually reset their clients. Not sure why I hadn’t done earlier ¯\_(ツ)_/¯ _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
