accessing secured services and GCX security provider
I'm not understanding how to work with secured services with the HTML5 viewer. Silverlight viewers for the same sites with GCX security and secured services prompt correctly for credentials. I'm not familiar with how security works between Essentials and AGS. I'm not using any type of Windows authentication. Any ideas what concepts I'm missing or what I need to do?
I have the following setup:
Staff site, (http://webmap.sanmiguelcounty.org/MobileViewer_1_2_1/Index.html?viewerConfigUri=http://webmap.sanmiguelcounty.org/Geocortex/Essentials/REST/sites/Staff/viewers/StaffMobile/virtualdirectory/Resources/Config/Default/Desktop.json.js) HTML5 viewer
- secured with GCX, no SSL
- all unsecured services
- prompts for credentials, works fine
Emergency services site, (http://webmap.sanmiguelcounty.org/MobileViewer_1_2_1/Index.html?viewerConfigUri=http://webmap.sanmiguelcounty.org/Geocortex/Essentials/REST/sites/Emergency/viewers/EmergencyMobile/virtualdirectory/Resources/Config/Default/Desktop.json.js) HTML5 Viewer
- secured with GCX, no SSL
- mix of AGS secured and unsecured services, using token-based authentication as set up through AGS's built in store
- does not prompt for credentials, just shows a blank screen with no banner or tools or map. Error in console says
_ssl: undefined
code: 401
details: Array[0]
get stack: function () { [native code] }
log: undefined
message: "Access to this resource requires authorization."
set stack: function () { [native code] }
tokenService: "/Geocortex/Essentials/REST/sites/Emergency/authenticate"
__proto__: d
- As soon as I disable GCX security, the viewer loads fine, but without prompting for credentials
-
Hi Heather,
It looks like you must configure the proxy page for the HTML5 viewer to be able to load secured sites.
I noticed in the configuration for the viewer that is not prompting for credentials, that there is no proxy specified. Can you try enabling the proxy for the Emergency Services site, and see if that makes a difference?
-Victoria
0 -
Victoria, thank you for your response. I went down another rabbit hole today, but will give the proxy page a try.
0 -
Thank you, that seems to have worked! I set up the default proxy as per the HTML5 documentation, got the credentials prompt and was able to log in.
0 -
I had to do one more thing to get my workflow on these sites to work. I have an address search with an autocomplete box for street name, and that layer is in the secured service, so I was getting security prompts at weird junctures. I found a variety of threads on the forums and came up with the following, which seems to work, although I'm not sure why or whether there is a cleaner way.
1) I added a Generate Token activity before the Display Form activity. For future workflow novices like me, the settings were:
Token service URL: "http://<servername - actually fully qualified in my case>/arcgis/tokens"
User Name/password: "valid user"/"pw" on the ArcGIS secured service
IP Address: blank
Referrer: blank
Expiration: blank
Token: _token (variable name)2) Then I added at Runtime Modification to the Display Form activity.
Assign activity
form.Find(of AutoCompleteBoxFormItem)("AutoCompleteBox1").Token = _token
where "AutoCompleteBox1" is the name of the form element, and _token the variable containing the Token generated earlier.Hope this helps someone else.
0 -
/customer/servlet/servlet.FileDownload?file=00P6000000eluKxEAI I too am trying to get global search to work against secured services, and am wondering if you ever got it to work? For my workflows, I added the token variable in and got them all to work, but when I key an address in the global search I am getting an authentication screen as seen below. In short, how are tokens passed to the Global Search? Thanks for any help.
0 -
Jim, I did not get the global search to work with secured services. I unsecured all services but the one I *have* to, and made that one not globally searchable.
0 -
Heather,
Thanks much for your reply. That seems like an undesirable solution to a software shortcoming. Hopefully the issue will be addressed in a future release. Until then I guess I'll have to disable the global search module.
Thanks again.
0 -
This issue is due to a bug which has been fixed for version 1.3 of the HTML5 Viewer, which should be released soon.
-Victoria
0 -
Hi Jim and Heather,
We've fixed an issue where tokens were not getting passed correctly with the global search as part of the 1.3.1 version of the HTML5 Viewer, which is now available for download. This should allow you to search your secured services.
0 -
I can confirm the 1.3.1 fixed our searching problems with secure services - which is all the services in map.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
10 kommentarer