Select to view content in your preferred language

What is the underlying purpose of the "Use external browser for sign-in" option?

64
0
2 weeks ago
Labels (1)
ToddTurner2
Occasional Contributor

We had some enterprise SSL certificate changes over the weekend. We believe we've made all necessary updates to Windows server cert stores, and Esri application cert stores. Since then, our QuickCapture and Survey123 fail to pick up the new certs and won't login the same way as before. We've found some work arounds, but need to understand what broke and why.

We are using ArcGIS Enterprise 11.1, and iPads with the Esri field apps

We have been using a URL like this to connect QuickCapture to our Enterprise 11.1 Portal for the last two years:
https://<fully qualified server name>:7443/arcgis

Since the weekend, that now generates the message:
"Warning  The server you are trying to connect to cannot be verified. Do you wish to continue?  Cancel  Accept"  (It's a cert problem)
Tapping Accept then generates the same message. Tapping it again then just gives a blank screen in QC.

We have found that utilizing the  "Use external browser for sign-in" option gets us in successfully with full functionality.  (Though, the first time yields a "No Client Id" message on a Portal Administrator page. After signing in there once (getting a token?), the "Use external browser" option from QC works fine.)

Why does this option work? Why is it there? What is it circumventing or compensating for?

If you're wondering why we don't connect via web adaptor, that's an entirely different issue. We can connect via IIS web adaptor fine, but don't get full functionality. Specifically, new projects with MMPKs will not download. We spent months trying to solve that one, gave up, and went to the direct 7443 connect, which has worked fine for two years until this week.

0 Kudos
0 Replies