CORS issues querying a secured ArcGIS Online (AGOL) layer that’s registered in ArcGIS Enterprise.
Hi everyone,
I’m reaching out to the vertigis WF5 community to see if anyone has encountered/overcomed CORS-related issues when running a VertiGIS Studio Workflow on-premises, specifically when querying a secured ArcGIS Online (AGOL) feature layer that’s registered in ArcGIS Enterprise.
In our setup:
The AGOL layer has been added to our onPrem Enterprise Portal as an item with embedded credentials.
The workflow is accessing the Portal item, not the direct AGOL URL.
Our VertiGIS Workflow domain (e.g. https://ABC/vertigisstudio/workflow) is slightly different from our Enterprise Portal domain (e.g. https://XYZ/portal/home), but this hasn’t caused issues when accessing other Portal-hosted services.
However, when the workflow attempts to query the AGOL-based layer, we’re seeing a CORS error in the browser console. Interestingly, the layer draws fine in the VertiGIS Studio Web app and Enterprise, so the issue seems to be isolated with workflow sandbox and the workflow service.
We’ve tried:
Registering the all the domains using the Register CORS URL workflow configuration. (ie the portal,AGOL and vertigis)
Adding all the domains to the ArcGIS Enterprise Allow Origins/ trusted server list.
Neither approach has resolved the issue.
Has anyone run into something similar or have suggestions on how to resolve this?
Thanks in advance!
-
We ran into a similar issues trying to load layers from AGOL to our Enterprise Portal application. Our solution was to create an API key on AGOL and make web requests manually in our workflow. It has worked well so far, the only pain point has been ensuring the API key is refreshed as necessary.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar