Hi
I'm working on porting our organization's main map viewer (WAB Developer Edition) to Experience Builder. I'm using the 1.16 version of the Developer Edition since we are deploying locally and intend to tweak it to fit our organizational needs as we did with WAB. I've understood the functional parity to not be quite there, but figure I can do what I can while Esri is working things out.
When loading a secured map it pops up a generic login window which only works with built-in accounts instead of redirecting to our Portal's login page. Utilizing the Portal login page is critical functionality that we need since we rely on using single sign for our users to access it.
Is there something I'm missing in the application configuration, or is this something that is a known bug with a (hopefully planned) fix on the way?
How it should work (as it does with WAB):
https://maps.fayetteville-ar.gov/viewer/index.html?webmap=6efeffe677914c06b0736f7beb092887&config=ed...
How it is currently working for us in EXB:
https://maps.fayetteville-ar.gov/newviewer/index.html?webmap=6efeffe677914c06b0736f7beb092887&config...
Solved! Go to Solution.
There are two issues that may be at play here. If the login prompt is happening when you first open the application, try adding the AppID to the config.json as described here.
https://developers.arcgis.com/experience-builder/guide/deployment-topics/#deploy-the-experience
If the prompt is appearing randomly after the application has already been opened, there is a known bug related to how SSO is handled in ArcGIS Enterprise. I don't know of a good fix for that one and I get a lot of complaints about it.
There are two issues that may be at play here. If the login prompt is happening when you first open the application, try adding the AppID to the config.json as described here.
https://developers.arcgis.com/experience-builder/guide/deployment-topics/#deploy-the-experience
If the prompt is appearing randomly after the application has already been opened, there is a known bug related to how SSO is handled in ArcGIS Enterprise. I don't know of a good fix for that one and I get a lot of complaints about it.
Adding the AppID to the config.json did the trick! Thanks for the help.
I guess I didn't read the manual.