Hi all,
I have one more glaring obstacle before deploying Field Maps. I am on Portal and we currently host images (as builts) on Amazon S3. I have custom attribute fields to hyperlink to these images, which work well within the web apps (in the browser). This is because the user is signed into Portal on the browser and requesting access to Portal data, which S3 uses as permission to view images. These images can't be public, so this layer of security is necessary.
In Field Maps, the user is signed into the Portal as well (on the app). When clicking that same URL field as mentioned above to open the hyperlink to the image, Safari opens and access is denied. This is because the link is opened in Safari and the session of Safari is either not logged into Portal or S3 has no way of knowing the request is coming from Portal (I have tested with public images and they open instantly). So even though Field Maps is signed into Portal, there's no way to pass that info along to S3 it seems. We checked logs to see how the s3 requests look. The "referrer" field shows what map or URL the request came from. The normal web app users generate the map URLs they are requesting from whereas the Field Map users just generate "-".
I doubt there is anything I could do to fix this at this point, it would seem that Field Maps would have to use some internal web viewer or something, sort of like it's login page. Very well may be wishful thinking.
Another potential workaround which I also haven't been able to get:
We have an app installed on the users phones to access these S3 images outside of GIS (search/download/etc.). The app says it can "open itself" with a url prefix before the URL. These can calculated into fields just like the normal images discussed above. However, throwing this into Field Maps just shows up as plain text and I can't have it open the app and go to it's location, which would be a great workaround.
These are most likely shots in the dark, but wanted to bring it up here before esri support.
Thanks,
Brendon
