ArcGIS Pro authentication stops when Portal and ArcGIS Pro are installed on the same machine

prmhara

Hi all,

The question is about ArcGIS Pro authentication however it is an issue with Portal configuration, that's why I am posting my question here in Portal group. The issue is that ArcGIS Pro is just waiting for authentication for a long time without any success.

At first let me describe the case when Pro can start successfully: when Pro is started from a Windows PC with licensing configuration as below.

 

And next case, for some test we need to install ArcGIS Pro on the same server machine with the Portal. However when I start Pro on this machine the authentication just shows an authentication waiting screen. The authentication step is not finished and ArcGIS Pro does not show its menu screen.

Configuration of the server where Portal and Pro are installed is as follows:

Enterprise 11.5 Portal for ArcGIS
Web Adaptor is not installed
The server machine is located in a private network
Portal is running on https://local-domain-name:7443/arcgis
WebContextURL configuration: {"WebContextURL": "https://example.com/portal"}
The domain example.com can be publicly accessed however the URL is not available when accessing from the local machine.

How to enable ArcGIS Pro authentication with the above configuration? Is Web Adaptor required to redirect https://local-domain-name:7443/arcgis to https://example.com/portal on the local machine?

Many thanks

OzanCanT

Hi @prmhara ,

ArcGIS Pro probably may be able to connect to a Portal even if no Web Adaptor is installed. In that case, it usually tries to communicate with the Portal’s Owning System URL, which is typically:
https://<machine-name>:7443/arcgis

In your setup, however, the WebContextURL is configured as:

https://example.com/portal

 

When a WebContextURL is set for Portal, ArcGIS Pro will attempt to access that URL. Since this address is not reachable from the Portal machine itself (as I understand from your description), the sign-in flow may not complete and Pro can appear to hang on the authentication screen.

If you have a federated or hosting ArcGIS Server, adding a Web Adaptor after can sometimes introduce additional complications because of URL changes. This probably means the local machine also needs to be able to reach the WebContextURL, or the URL should be properly redirected.

Also, the Web Adaptor for Portal is very important and necessary for deploying Portal effectively as described in following documentation:
https://enterprise.arcgis.com/en/portal/11.5/install/windows/about-the-arcgis-web-adaptor.htm

Hope this helps.