Solved: Re: Webex unstable?

finnk · ‎10-05-2022

Hey,

We faced some issues yesterday and today. We implemented SSO with webex using the opened interface (https://developer.webex.com/docs/login-with-webex)

Yesterday we first got an unexpected issuer (https://idbroker.webex.com/idb instead of expected https://idbroker-eu.webex.com/idb) which led to token validation problems.

Today first our App disappeared first from the developer portal and we got other issues. Now it is working again...for now.
We never had any problems with webex SSO

It seems like the webex API devs are making changes that are causing problems.

Can you verify? Is there any site where I can get updates? This is critical.

Thank you & best regards

Raffaele Lagana · ‎10-05-2022

Ok thanks for this information. Our engineers just resolved an issue which affected multiple services, one of our servers (in EU) was having a huge spike in CPU load. Possibly this affected the functionality you refer to, meaning it got redirected to idbroker instead of idebroker.eu, at least temporarily. It sounds plausible but we'd have no way to check that really and it wouldn't be our area of expertise.

As for the other issues you mentioned where "the token endpoint was not available and our App on the developer portal was removed", I am more confident in saying that this was caused by the issue on our servers that I explained above. Engineering had to move the developer portal temporarily to another server, so that it continued working. This might have caused the temporary issues you faced.

But this issue only happened today so anything you experienced yesterday would not have been related to this.

View solution in original post

finnk · ‎10-05-2022

Thank you for your reply. We used different users. We all got redirected for sign-in to "https://idbroker-eu.webex.com/idb/....." but then the issuer was set to "https://idbroker.webex.com/idb " while the expected issuer was still "https://idbroker-eu.webex.com/idb"

This was solved automatically after some time, so I couldn't dig deeper into it. Yesterday I temporarily disabled the issuer validation as a hotfix, but today when I investigated, everything was fine again. Now we allowed different regions for the issuer by setting up a custom Issuer validator using Regex.
Later today we faced some other issues, the token endpoint was not available and our App on the developer portal was removed.

After a few minutes, everything worked again, but I got the feeling that Webex had some internal problems...

Raffaele Lagana · ‎10-05-2022

Ok thanks for this information. Our engineers just resolved an issue which affected multiple services, one of our servers (in EU) was having a huge spike in CPU load. Possibly this affected the functionality you refer to, meaning it got redirected to idbroker instead of idebroker.eu, at least temporarily. It sounds plausible but we'd have no way to check that really and it wouldn't be our area of expertise.

As for the other issues you mentioned where "the token endpoint was not available and our App on the developer portal was removed", I am more confident in saying that this was caused by the issue on our servers that I explained above. Engineering had to move the developer portal temporarily to another server, so that it continued working. This might have caused the temporary issues you faced.

But this issue only happened today so anything you experienced yesterday would not have been related to this.

finnk · ‎10-05-2022

Ok great. That makes sense. Thank you for the insight.

Raffaele Lagana · ‎10-05-2022

The idbroker links you mentioned are expected depending on what region a user's org belongs to. If it's in US, you will get routed to https://idbroker.webex.com/idb and for EU you will get routed to https://idbroker.eu.webex.com/idb . Not sure exactly how you configured SSO but the above routing I explained is normal for authentication. Which user did you use for this?