AnsweredAssumed Answered

Unable to log into ArcGIS Server Manager after Federating

Question asked by lscharen on Jun 2, 2017
Latest reply on Dec 11, 2017 by lscharen

I have federated Portal 10.5 with a single-machine ArcGIS Server 10.5 site.  Portal is configured to use Active Directory for its Identity Store. Portal and ArcGIS Server are on different virtual servers and their respective web adaptors are on a separate Web Server and configured under different IIS sites. I have done ArcGIS Enterprise Basic deployment in the past successfully.


This table summarized the configuration


URLDescription Adaptor pointing to the ArcGIS Server Adaptor pointing to the Portal for ArcGIS Site URL to the ArcGIS Server machine URL to the Portal for ArcGIS


Almost everything appears to work correctly.  For example

  • I can log into Portal using the primary site administrator account
  • I can log into Portal using my Domain account
  • After Federating, all of the ArcGIS Server services appeared as Portal items, as expected
  • I can log into the ArcGIS Server Administrative service directory using the ArcGIS Server site administrator credentials, or by manually generating a Portal token.


The only issue if that attempting to open ArcGIS Server Manager fail.  The interface hangs on the "Please wait..." progress bar and the network traffic shows repeated failures to POST to the portal generateToken page via the ArcGIS Server proxy****… 


The network inspector shows that ArcGIS Server returned a 500 server error caused by a "Connection closed" (see screenshot).


Are there any good ways to go about diagnosing the root cause of an issue like this?



Installing Fiddler and enabling HTTPS traffic snooping shows that request is being sent from the ArcGIS Server machine to the Portal Web Adaptor.


This may be a side-effect of enabling Fiddler as a MITM proxy, but the Portal logs show this WARNING:


ArcGIS Server services URL '' cannot be validated against ''. If the service URL is a proxy URL verify it is accessible to clients.


The JSON at the /info endpoint is

{  "currentVersion": 10.5,  "fullVersion": "10.5.0",  "soapUrl": "",  "secureSoapUrl": null,  "owningSystemUrl": "",  "authInfo": {   "isTokenBasedSecurity": true,   "tokenServicesUrl": ""  } }

What information is being used to attempt this 'validation'?