Exception: Unable to generate oauth token

[TZ]

I am trying to Connect to ArcGIS Enterprise v11.1 using a built-in account as described in tutorial --> https://developers.arcgis.com/python/guide/working-with-different-authentication-schemes/#User-authe...

Here is my entire code:

---------------------------------------------------------

from arcgis.gis import GIS

portal_url = 'https://myserver.org/portal/portaladmin/'

username = 'portaladmin'

password = 'pasw1234'

print("Portal for ArcGIS as a built in user")

gis = GIS(portal_url, username, password)

print("Logged in as: " + gis.properties.user.username)

------------------------------------------------

i get this error:

Exception: Unable to generate oauth token

How to solve this? Do i have to register this simple script as an App in Azure AD or something?

[EarlMedina]

Remove "portaladmin". It should be: "https://myserver.org/portal" from your example.

[TZ]

I changed the "portal_url" value to "https://myserver.org/portal" as per your suggestion but still get the same error "Unable to generate oauth token", the only difference being an informational message "Portal for ArcGIS as a built in user" in the output at the very beginning.

Are there any more guides regarding setting up OAuth for ArcGIS Python API aside this very scant page ? --> https://developers.arcgis.com/python/guide/working-with-different-authentication-schemes/#User-authe...

[TZ]

and what about my previous question - do i have to register this modest script as an app in Azure AD or not??

[EarlMedina]

Are you saying this is in fact not a built in user? Are you actually using Azure AD? DO you happen to know how the portal was sconfigured?

[ellipsol]

I started seeing this same issue that started yesterday. Do you have a solution or work-around? I've been using this calls in scripts for more than a year, no problem until now.

[ellipsol]

My proxy changed and that was what was causing this error. It is resolved now.

[Danfranco]

where are you specifying the proxy changes? I have a very similar issue, but I know nothing has changed....