topic Re: Integrations & Authorization with a proxy in Webex for Developers

Integrations & Authorization with a proxy

gary.charvier — Thu, 24 Feb 2022 20:09:52 GMT

Hi all,

I'm trying to setup a Proof of Concept for my company in order to demonstate how Webex is better than our current tool.

I'm setting up the login with the help of the documentation (https://developer.webex.com/docs/integrations)

I already created the "integration" mock app and got my client id & client secret.

My code is done in Angular/NodeJS per company policy.

With a call to the https://webexapis.com/v1/authorize ressource, I get back a code, as expected.

My problem happens when calling the https://webexapis.com/v1/access_token URL.

By a direct call via Postman, I get back the expected data

By a call via a localhost Express server on my private computer, I get back the expected data

By a call via a localhost Express server on the company computer, I get back en error : "getadrrinfo ENOTFOUND webexapis.com"

I bet the problem lies with the company proxy or something of this kind, but I can't really ask my admin system to the rescue, since this is an unofficial PoC for now.
I head the possibilité to setup a NTLM authentication first, but I have absolutely no idea how to do that. I didn't find any sample online to do NTLM while seding a POST request.
Did anyone have a similar issue? If so, how did you resolve it ?

Re: Integrations & Authorization with a proxy

dstaudt — Tue, 15 Feb 2022 20:28:16 GMT

The error suggests to me that the app platform is unable to resolve webexapis.com via DNS, e.g if you try to ping webexapis.com (or another domain, like yahoo.com) you get a name lookup failure.

Re: Integrations & Authorization with a proxy

gary.charvier — Wed, 16 Feb 2022 08:49:26 GMT

that's exactly what happens. Do you have a solution?

Re: Integrations & Authorization with a proxy

dstaudt — Wed, 16 Feb 2022 19:18:30 GMT

Just general networking DNS troubleshooting things, but going to be platform/OS specific:

* Check the network settings of the application's platform/OS. If the application/platform has a static IP address, either configure static DNS server(s) or enable DHCP configuration of DNS (but not IP).

* Make sure the DNS servers configured are applicable to the network environment, e.g. IT may have different DNS servers for staging vs. production environments.

* If you're feeling a little rogue, you could statically configure something like the Google DNS servers

* For truly janky temporary PoC-only, you can use your PC to get the IP address of webexapis.com and hard code that into your app. Note, this will break HTTPS certificate checking (you can likely disable that in your HTTP framework/library) and webexapis.com is of course not a single, static IP but a load/H-A balanced server farm behind DNS. The IP you get today may change at any point, or it may point to a busy server...

* You'll probably end up needing to contact your IT folks in the end anyway, but asking 'How can I get DNS to work for this app?' should be easy enough to get them started.