[cisco-voip] [External] Jabber Users Prompted To Accept Webex Cert

[Riley, Sean]

Did anyone come up with a solution to this, other than to tell the users to Accept the Cert?

We are completely on prem with no webex services.  Clients are v 12.9.6.  I was able to reproduce the issue once using a test user account, but have not been able to reproduce since, even after a Jabber reset.  Most of my team is running Jabber v 14.x and we have not seen the cert warning.

Does a user declining the cert add it to the Untrusted Certificates store in Windows?  Maybe that takes priority over a cert in the trusted store?

I have done the following, but we still have sporadic reports of the certificate warning from Jabber:


1.       Ensured the new IdenTrust Commercial Root CA 1 was in CUCM and services restarted on CUCM and IM&P.

2.       Added the HydrantID Server CA O1 to the computers trusted store via GPO.

Thanks.


From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Lelio Fulgenzi
Sent: Friday, November 12, 2021 3:17 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca>; Gary Parker <G.J.Parker at lboro.ac.uk>; Brian V <bvanbens at gmail.com>
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] [External] Jabber Users Prompted To Accept Webex Cert

Darn it. We've started seeing the alerts for some reason.

Can we just tell people to accept? Argh.


-----Original Message-----
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Friday, November 12, 2021 8:45 AM
To: Gary Parker <G.J.Parker at lboro.ac.uk<mailto:G.J.Parker at lboro.ac.uk>>; Brian V <bvanbens at gmail.com<mailto:bvanbens at gmail.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] [External] Jabber Users Prompted To Accept Webex Cert

(a) do this
(b) don't do this

Is my favourite part!

I remember when I first started, I had opened a case, then another, and got two very conflicting opinions from the TAC

(a) TAC suggests using the T train for voice gateways
(b) The TAC suggests staying away from T train for voice gateways

Or something like that.

When you're first starting out and have a crush on Cisco, it's very had to work through that.


-----Original Message-----
From: Gary Parker <G.J.Parker at lboro.ac.uk<mailto:G.J.Parker at lboro.ac.uk>>
Sent: Friday, November 12, 2021 5:24 AM
To: Brian V <bvanbens at gmail.com<mailto:bvanbens at gmail.com>>
Cc: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>; Johnson, Tim <johns10t at cmich.edu<mailto:johns10t at cmich.edu>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] [External] Jabber Users Prompted To Accept Webex Cert

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>


Yeah, I had a suspicion at one point that this might be to do with the telemetry (which we’re sending), but the only reference I can find to the servers used for this is in the "Feature Configuration for Cisco Jabber 12.8” doc where it states that clients connect to "metrics-a.wbx2.com” (also mentioning that you must install a GoDaddy root cert).

We’ve been sending telemetry for some time and have not had this problem before, and the cert the client is erroring on is idbroker.webex.com (with the IdenTrust root).

Fwiw, metrics-a.wbx2.com is a cname for ha-a-main.wbx2.com, which in turn is a cname for achm-main-ha-a-nlb-1d0e22049c746ef1.elb.us-east-2.amazonaws.com

metrics-a.wbx2.com *does* have a GoDaddy root cert, and a wildcard server cert.

What a mess!

That bug also says:

"b) Disable the telemetry call to Webex in the jabber-config xml”

…but then goes on to say:

"This error/popup is not related to Telemetry. Even if you disable Telemetry on Jabber certificate pop up will continue to show.”

¯\_(ツ)_/¯

Gary

> On 11 Nov 2021, at 22:57, Brian V <bvanbens at gmail.com<mailto:bvanbens at gmail.com>> wrote:
>
> Part of the workaround referenced in the Bug doesn't make sense. They reference adding some GoDaddy certs, but when you look at the URL they reference (*.wbx2.com) that is signed by Hydrant not Go Daddy.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20211129/0ae39f9c/attachment.htm>