We are having issues getting survey123 to work with IWA and non-federated feature services.
According to the release info in https://blogs.esri.com/esri/arcgis/2017/04/27/whats-new-in-version-2-0-of-survey123-for-arcgis/ IWA is supported, however we cant seem to make any headway.
We have a very specific workflow that we have been trying to get to work using non-Federated Feature Services and Survey123 with a server that uses web-tier / IWA authentication. We currently collect a lot of field data back to non-federated features services using Collector for ArcGIS which works well, however a similar workflow does not work for Survey 123.
Our Collector workflow at the moment is establishing the web services on our own infrastructure then adding these web services to an AGOL map. Using this webmap we are able to login to our AGOL, then using our organizational credentials authenticate for the individual feature services within that map. Collector pulls up an additional authentication window to do this.
So I have followed the following workflow:
Before the recent AGOL updates we were able to Add Item from Web (without embedding credentials due to the iwa) to generate a proxy service however we now get a “Required – Valid Service credentials not fully specified” Error.
Then from this Proxy we generated the Survey123 form and published successfully. With Survey123 on an IWA platform we could submit without issues as the authentication worked. However on a non IWA platform (IOS) we would get the 401 Unauthorized we submit the surveys. I would have thought at this stage Survey123 would recognise the 401 and pop up a credentials pop up to authenticate to the service. Is this the expected behaviour?
If I try and use our URL (not the Proxy) as the submission URL and then on publishing using version 2.3.24) I get “The custom feature service Submission_url is not compatible with this survey (Request Error Missing serviceItemId)”
Any help as to why we can’t add item from the web firstly in AGOL would be appreciated and then some knowledge around the expected behaviour in Survey123 when a 401 is returned, and then also why we cant use our URLs as a submission_url?
Thanks in advance
As we mentioned in the 2.0 blog post, IWA is supported in terms of connecting to Federated Services via a Portal. We currently do not have plans to support IWA ArcGIS Servers that are not federated; given the current architecture recommendations from the Enterprise team, we are focusing on full ArcGIS Enterprise implementations.
The submission_url error you are receiving is due to a change in submission_url required to work with federated services- to properly set up the form, we need to know the item if that a service has been registered under.
I don't have much knowledge of the issue you are seeing in the Map Viewer.
Thanks for the quick response James,
Our workflow requires us to have data exposed via AGS (IWA) (unfederated) and added as an item in AGOL for use with survey123. Is there any way of getting this to work? as we already have established workflows with ArcGIS Collector and would really like to implement the smart form capabilities of Survey123 together with this data.
Or is the only way to establish Federated Services with portal either IWA or Token based authentication.
Do you have any further ideas regarding this or know of anyone that can help. Specifically, when a 401 is returned to Survey123 it does not know what to do with it? However when a 401 is received by Collector it immediately pops up an input form to authenticate? Can you explain how Survey123 currently handles 401's
At the time, Survey123 is not set up to handle the ArcGIS Server configuration (stand-alone with IWA) you describe. If you require IWA support on ArcGIS Server, we would recommend that it be federated with an IWA Portal as part of an Enterprise implementation so that the security models of the Server and Portal (which manages the form item and relationship between the form and feature service) are aligned.