Why isn’t my secured layer working within Geocortex Web?
Security is important, but it can also be a barrier to accomplishing seemingly straightforward objectives.
If you are using Geocortex Web and you see “Layer Initialization Failed” on a secured layer one possible reason has to do with how Esri’s new JavaScript 4.x API works.
Since version 4.9 Esri has begun strengthening security and has included a trustedServers list that must be populated if you want credentials such as cookies and authorization headers to be passed through to that server.
See https://developers.arcgis.com/javascript/latest/api-reference/esri-config.html#request and search for trustedServer.
Even more challenging in the area of security is how requirements change over time. Your secured layer might work just fine inside of the Geocortex Viewer for HTML5 or inside Esri Web AppBuilder but not within Geocortex Web.
We are working to highlight cases where you are likely to run into this, and to give you an interface in Designer to address them. In the meantime, if you run into this and need to add a trustedServer Web does support this in the raw app.json.
{
"id": "viewer",
"version": "5.6.0",
"trustedServers": ["https://my-awesome-server.latitudeqa.com"],
"$type": "geocortex-web-viewer"
},
Please do feel free to reach out to us here on the Communities or via Support if you need assistance getting this working.
Cam
-
Is there an update on this issue? (e.g. will there be an interface in the Designer in 5.9).
We got this issue for a specific user of a viewer when opening the viewer outside the network of the organisation.
0 -
For clarity, the server to define here is the server where e.g. a webmap comes from?
0 -
Seems that saving that app after applying trustedServers to the app.json clears out the trustedServers parameter. This is on Web 5.18.1. Anyway around this? Is this going to be in the designer eventually?
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
3 commentaires