Get rid of the extra "Sign in " popup window when launching a secure VertiGIS Studio Web App
Planned
Current sign in behavior for a secure VertiGIS Studio Web Application registered with an ArcGIS Portal is like this: when an user launch the app, it first displays the Sign in prompt window (screenshot #1) before leading the user to the Portal's Sign in page (screenshot #2). If the user click "Cancel" button on the "Sign in" window, an error will be displayed (screenshot #3). The sign out landing page is also the "Sign in" prompt window.
I would like to request that VertiGIS Studio Web Application has similar sign in behavior as a Geocortex Viewer for HTML5 application authenticated by ArcGIS. It directly launches the portal's login page and it's sign out landing page is also the Portal's login page:
-
Official comment
The login dialog is the mapping SDK's own sign-in confirmation ("Sign in required… OK / Cancel"), not part of our UI. It appears when the app has to sign the user in through a popup window that the user didn't open themselves.
Why it appears. Browsers only let a page open a new window as a direct response to a user action such as a click or keypress. Many sign-ins start without one: when the app loads and the user was already signed in, when the portal requires sign-in up front, or when a secured layer or service is requested during startup. Since nothing the user did started these, the SDK can't open the sign-in popup directly. It shows the confirmation dialog to get a click and opens the popup from that click.
With the 5.45 release in December, we could complete some changes! Before the user has interacted with the page, there is no work to lose, so a startup sign-in now sends the whole page to the portal's sign-in page instead of opening a popup. That needs no new window, so there's no dialog and no popup blocker. The app notes that a redirect is in progress. When the portal sends the user back, the app finishes the sign-in and then switches to popups, so a cancelled sign-in doesn't send the user away again. The app's current URL state is kept through the round trip. Once the user clicks or types, sign-in switches to popups so later sign-ins don't navigate away from their work. When the user clicks "Sign in", the app opens the popup window right away, while the browser still links it to the click. The SDK then reuses that window, and the app closes it afterwards if it wasn't needed.
When the dialog can still appear. Redirects are turned off in two cases. The first is when the viewer is embedded in a frame, because portal sign-in pages won't load inside one. The second is when a host application such as Designer supplies the app config- in this case App Designer handle authentication.
-
I agree, our organization only allows SAML logins through Enterprise. Having this "Sign In" is redundant to Portal authentication. This should be a configurable option within Studio Web.
3 -
I empathize with the frustrations.
We can look at this more closely in the future, but no current plans to change it.
There is a TREMENDOUS amount going on behind the scenes with this stuff and we do our best to streamline it and still make all the use cases work.
-10 -
I agree to
1 -
I’m wondering if this has made it onto the development roadmap? It may seem like a little thing but it’s actually a significant barrier to adoption. Our users have a seamless AD integration with the HTML5 viewer. With VSW they’re presented with 2 authentication screens before they can access the map. This creates an opportunity for user error if they hit “cancel” as described in this post. It also just creates confusion for the user. I’ve had several support requests where they think there’s simply an error loading the map. Unfortunately, I feel we’re forced to use the HTML5 viewer until there’s a better login experience with VSW.
7 -
Any feedback on this?
4 -
With reference to my post under
https://support.vertigis.com/hc/en-us/community/posts/12086841047570-Client-required-to-login-each-time-a-VertiGIS-Studio-Web-browser-session-starts?page=1#community_comment_25463097288466
We have several former Geocortex customers who migrated to VSW as well as new VSW customers asking to get rid of the first sign in popup which frustrates the end users as it is perceived as a completely useless action. One these organisations is now even considering working with the SDK to avoid the behavior. If it can't be fixed in VSW, does anybody have experience with achieving this based on the SDK?8 -
I wanted to echo the sentiments outlined above. It is a significant barrier to user adoption and a complaint we receive often. We have over 500 intended users and our less technologically tolerant groups are incredibly frustrated by it.
7 -
We have many complainst from our users that they have to press Ok before they can use the maps. Please remove this.
4 -
Yes, please remove at least the first prompt.
6 -
Cam Barnard I haven't seen this dicussed at all in the Road Ahead videos. Is this on the development road map at all?
2 -
Any feedback on this?
2 -
can you push this one into the development roadmap? Cam Barnard
3 -
Has anyone used a 3rd party Single Sign-On (SSO) identity provider to fix this issue?
0 -
Yes, please remove the first prompt.
1 -
It would be nice to have one less click for a simpler sign-in experience. Thanks.
1 -
Our users will not like this addition sign-in.
1 -
I wonder if the extra "Sign in" popup window cause issues for refresh token? and creates a frustrating user experience?
2 -
Our clients express the same wishes; their users find this frustrating and would like to perform less “clicks”.
2 -
This has also been a point of frustration among our clients. Is it set to “not planned” indefinitely, or is there a chance it will be taken into consideration in the future?
5 -
This has been a pain point for our users since we migrated from Geocortex to VisualStudio. The GCX experience was streamlined and user friendly. This login policy for VertiGIS is frustrating for end users. VertiGIS - please listen to your users on this one!
5 -
Is there any news about this situation yet? It's been really quiet from VertiGIS.
5 -
There are several similar questions about this topic.
It appears the answer to this question is to migrate to Esri Experience Builder?
0 -
Due to this unfortunate behavior, we have had to make our VertiGIS Web applications publicly accessible within our firewall to bypass the login process, which is far from ideal.
0
Please sign in to leave a comment.
Comments
24 comments