PROBLEM
In a highly-available ArcGIS Enterprise (HA) deployment, users may experience abrupt, intermittent logouts during browsing sessions. This behavior suggests a potential issue related to session persistence, often caused by misconfigured load balancers or improper handling of sticky sessions, which are critical for maintaining continuous user authentication across multiple nodes in an HA environment.
In a highly-available ArcGIS Enterprise deployment, if the PrivatePortalURL property is not explicitly configured, it defaults to the Fully Qualified Domain Name (FQDN) of the primary portal machine—for example: https://machine-pfa1.domain.com:7443/arcgis. You can verify this setting via the Server Admin Directory under: Security > Config > Portal Properties.
The PrivatePortalURL is used by ArcGIS Server for back-end communication with the portal. When the primary portal is offline and only the standby is accessible, ArcGIS Server still attempts to reach the primary portal using the default FQDN. This mismatch causes login prompts, as the server is unable to successfully authenticate with the expected back-end portal.
Note:
PrivatePortalURL tells the server how to reach the portal internally, typically through a load balancer or proxy URL configured for high availability.
{"WebContextURL":"https://fqdn.domain.com/portal","privatePortalURL":"https://fqdn.domain.com/portal"}
Note: The FQDN here stands as the public facing DNS Alias.
The above change allows for Server's back-end communication to go to both the primary and standby portals.
Article ID: 000036150
Get help from ArcGIS experts
Start chatting now