This...may be complicated to explain. We are trying to create Feature Service webhooks in ArcGIS Enterprise. ESRI documentation indicates that this can either be accomplished with the admin Portal (which very few users have access to) or via the “administrative API”
https://developers.arcgis.com/rest/enterprise-administration/server/create-webhook/
The only way to access the administrative API is to acquire a session token (SSO, username/password, other authentication types are not accepted).
In ArcGIS Enterprise, the generateToken endpoint is no longer used, the OAUTH2 “Token” endpoint has superseded it. There is a preliminary authorization step that must be completed before accessing the “Token” endpoint.
https://developers.arcgis.com/rest/users-groups-and-items/authorize/
https://developers.arcgis.com/rest/users-groups-and-items/token/
Authentication in our environment is done via OAUTH2/SAML so when trying to access the “Authorize” endpoint via an HTTPCALLER, the response that I’m getting is an HTML response that kind of looks like it’s just the user sign-in page. I’ve tried the “Use Authentication” setting in the HTTPCALLER with both a standard Portal web connection, and an OAUTH Portal web connection with the same results.
I can get the Authorize endpoint, the Token endpoint, and the create webhooks endpoints to work correctly directly via web browser. But my ultimate goal would be to build an FME front-end (web app via FME Flow) with user parameters that would match what is requested by the ArcGIS administrative API. This would be a really cool workflow, but won’t be able to work without being able to generate the token in FME.
Any thoughts?
