Limitations in Experience Builder's Basemap Gallery with Disabled Anonymous Access

EddieFung1

In our organization, the "Allow anonymous access to your organization" Security Policy is intentionally disabled.  Although we serve specific content publicly for use in public-facing applications, we do not intend for our organization to be accessible for viewing and navigation by anonymous users. 

Since 2019 we have used a custom basemap gallery group to serve public-facing WAB/EXB applications with our custom, publicly-accessible basemaps.

After moving to Experience Builder, we encountered [BUG-000167252: In ArcGIS Experience Builder, the Map and the Basemap Gallery widget do not display a publicly shared custom basemap if the 'Allow anonymous access to your organization' setting is turned off.]

and Esri have officially flagged this issue as "As Designed" and updated documentation with this note.

• If basemaps are not displaying for some users, it may be because your organization does not allow anonymous users to view your organization's content. Administrators and those with appropriate privileges can allow anonymous access in organization security settings.

In order to continue to serve the public with our custom, publicly-accessible basemaps through Experience Builder, a significant amount of work is required to review and modify our organization site to enable anonymous access.  We would like to avoid this by allowing the Experience Builder Basemap Gallery Widget to include the option to manually configure which public web map to use, much like how Web AppBuilder Basemap Gallery Widget used to allow.

Brian_McLeer

We have a similar situation. One workaround we are thinking of doing is through the basemap gallery widget. In a fairly recent release of EB, you can configure custom basemaps. It is an additional task to set it up, but might work for not having to change the anonymous access settings.