<div dir="ltr">
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:black;background:white none repeat scroll 0% 0%">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.<span></span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:black;background:white none repeat scroll 0% 0%"><span> </span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:black;background:white none repeat scroll 0% 0%">Not clear why IdenTrust is missing on your
computers. <span></span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:black;background:white none repeat scroll 0% 0%"><span> </span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:black;background:white none repeat scroll 0% 0%">Guessing maybe you disabled automatic root
updates at some point or don’t have Windows updates running ? <a href="https://serverfault.com/questions/752146/why-are-many-admins-using-turn-off-automatic-root-certificates-update-policy" style="color:rgb(5,99,193);text-decoration:underline">https://serverfault.com/questions/752146/why-are-many-admins-using-turn-off-automatic-root-certificates-update-policy</a></span><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;background:white none repeat scroll 0% 0%"><span></span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;background:white none repeat scroll 0% 0%"><span> </span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:black;background:white none repeat scroll 0% 0%">Cisco Field Notice we didn’t notice</span><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif;background:white none repeat scroll 0% 0%"><span></span></span></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:"Calibri",sans-serif"><a href="https://www.cisco.com/c/en/us/support/docs/field-notices/721/fn72120.html" style="color:rgb(5,99,193);text-decoration:underline">https://www.cisco.com/c/en/us/support/docs/field-notices/721/fn72120.html</a><span></span></p>
</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 11, 2021 at 6:22 AM Gary Parker <<a href="mailto:G.J.Parker@lboro.ac.uk">G.J.Parker@lboro.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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 <a href="http://idbroker.webex.com" rel="noreferrer" target="_blank">idbroker.webex.com</a><br>
<br>
This thread on <a href="http://community.cisco.com" rel="noreferrer" target="_blank">community.cisco.com</a> (<a href="https://community.cisco.com/t5/unified-communications/jabber-idbroker-webex-com-certificate-request-during-the-first/td-p/3216376" rel="noreferrer" target="_blank">https://community.cisco.com/t5/unified-communications/jabber-idbroker-webex-com-certificate-request-during-the-first/td-p/3216376</a>) showed we weren’t the only ones, but that it seemed limited to managed clients.<br>
<br>
We solved this by adding the EXCLUDED_SERVICES=WEBEX flag to the installer on our managed clients.<br>
<br>
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.<br>
<br>
Is anyone else seeing this today?<br>
<br>
As a workaround I’ve added:<br>
<br>
<ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices><br>
<br>
...to our jabber-config.xml, but that will require users to manually reset their clients. Not sure why I hadn’t done earlier ¯\_(ツ)_/¯ <br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>