Deployed Experience Builder Developer Edition 1.19 - Sign In Experience

Question

I am using Experience Builder 1.19 Developer Edition with custom widgets. I have deployed an application to an internal web server and everything works well once the app loads.

But, when the web app loads in the browser, users first get a small dialog box that says "please sign into ArcGIS online - OK or cancel. " If they click ok they get the sign in page. But this is a strange end user experience, as the user just expects the sign in page straight away. Is there a way to bypass this little extra dialog box, perhaps using the new Login widget? ( I saw this post from 2023.)

This behavior happens when I select "apply builder client ID" to my app download from the builder environment. When I leave "apply builder client ID" unchecked, the app loads (after a different sign-in prompt), but seems to "timeout" after 30 minutes and loses connection to hosted feature layers in my web map. End-users then see a credentials banner with a sign-in option but a sign-in using this credentials banner does not fix the app. They are required to refresh the app in the browser to continue working.

All the data in the web map is hosted in ArcGIS Online. I appreciate any insight.

Devon_Hedemark · Answer

Good morning, @Brian_McLeer

Thanks for the response. You are correct about those steps. If I select the "Apply builder client ID" checkbox when I download my ExB DE app, I notice it does add the client ID to the config.json in the CDN folder as you noted. Also, I added the internal web server URL to the Experience Builder Credentials OAuth 2.0 application in my Portal (AGO), as an additional redirect URL with the https://localhost:3001/ URL used by the builder. This was required in order for the end users to see a proper sign-in pop-up. But, it still shows one extra dialog box that says "please sign into ArcGIS online ".  If they click "OK" they get our organizations sign-in page and can login as expected.

This is not too big of an issue, but it does require an extra click for the end users that was not required for my Web AppBuilder (WAB) apps.

Based on the response to the previous thread on this topic from 2023 by @Wei_Ying, it sounds like it is designed to prevent the login popup from being blocked by the browser and then user sometimes will not notice the blocked login.  But I thought this may have been improved in the latest version of ExB, perhaps using the login widget on a splash screen or something like that.

Brian_McLeer · Answer

Hello @Devon_Hedemark , you may need to create an OAuth 2.0 application in your Portal with a client ID for the internal URLs and add the redirect URLs under the Settings. The client ID will also need to to be pasted in the deployed application CDN folder number config.json. If you search for clientID and enter the client ID between the double "".