You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like an instance of ArcGISIdentityManager that uses a custom portal url will still make a request to www.arcgis.com/sharing/rest/oauth2/validateAppAccess when calling instance.validateAppAccess(myClientId).
Shouldn't this instead try to validate the user's app access against the configured portal? I can see that my manager's portal property is set to my custom portal url after creating it via deserialize({ portal: 'myCustomUrl', ... })
From looking at the code it might be enough to pass the third parameter (portal: string) to validateAppAccess:
It looks like an instance of
ArcGISIdentityManager
that uses a custom portal url will still make a request towww.arcgis.com/sharing/rest/oauth2/validateAppAccess
when callinginstance.validateAppAccess(myClientId)
.Shouldn't this instead try to validate the user's app access against the configured portal? I can see that my manager's
portal
property is set to my custom portal url after creating it viadeserialize({ portal: 'myCustomUrl', ... })
From looking at the code it might be enough to pass the third parameter (
portal: string
) tovalidateAppAccess
:arcgis-rest-js/packages/arcgis-rest-request/src/ArcGISIdentityManager.ts
Lines 1193 to 1197 in 090e3a5
I'm happy to work on a fix for this if someone can confirm that this is a bug.
The text was updated successfully, but these errors were encountered: