OAuth update failing to connect

[Charlie-New]

We've started the migration to the OAuth setup in the Developer console and are using the 2.10.0 sync version but cant get the script to connect. The connector files seem to be set correctly but the logs just show - umapi_client.connection - UMAPI connection error

The migration tool in the admin console doesnt show any successful OAuth attempts and cant seem to get it to connect using the new executable instead of the pex file. Is there some other config we're missing?

[Luci2015]

there may be different root causes for this, but from experience I can tell you it's not the script, nor the UMAPI service, it's a local setup that blocks the tool from connecting to the 2 API endpoints.

• is the traffic is proxied?
• is there an HTTPS_PROXY env variable set up now, or is it set up at runtime in the batch file/shell script/ ps script?
• the machine hosting the tool -> is it on-prem or cloud?
• firewall setting (outbound) - allowlists up to date for the 2 endpoints used? ims-na1.adobelogin.com / user management.adobe.io
• running account has permissions to call outside your network?

[Charlie-New]

Hi, yes the traffic is proxied and there are environmental variables setup on the Windows server side. Its an on prem server with the local firewall disable
Using the older .pex file with JWT seems to work ok but not the newer .exe with OAuth, do they use different URL's at all?

[Luci2015]

in this case just the HTTPS_PROXY env variable is important.
what value you have for it? I am interested only in the first part where it's described the protocol, not the actual proxy name and port

[Charlie-New]

The https_proxy environment variable on the server points to our company proxy address, that's from the local server environment variables, so https://x.x.x.x:xxxx

[Luci2015]

change https:// to http://

[Charlie-New]

There is also already a http entry in the Windows environmental variables with the same proxy setting (but with http)

[Luci2015]

it's not what I meant!
UST is only interested in the https_proxy one. You can even remove http_proxy, if unused by something else internally..
What I meant is that you should change https_proxy to this format:
https_proxy = http://proxy:port

[Charlie-New]

Apologies, yes we've tried setting the https variable to the http:// setting as well but still get the connection error

[Luci2015]

if you know for sure that the proxy is present and the values for it are correct (including its port), then try this:
open a new cmd window with admin privileges, then type (replace with your own values below):
set https_proxy=http://yourProxy:port
now try running the tool (same cmd window) using command line:
user-sync.exe -t

[Charlie-New]

Thanks that pointed us in the right direction, updated our scripts to statically include the proxy settings and that seems to be connecting out now