I've created a 3-tiered deployment of ArcGIS Enterprise 10.8 on Azure VMs (actually, it's 4-tiered if you count adaptor).
The following configuration is working correctly:
Web Adaptor (Portal) --> Portal --> Server --> Data Store
Next, I've added a second Server machine to my ArcGIS Server site. This all seems to work fine, except that when I attempt to log in to ArcGIS Server Manager on the second Server machine, the login hangs on the "Please wait..." progress dialog.
Looking at the network calls, the call to generate token:
https://webadaptor0/arcgis/sharing/generateToken?request=getToken &serverUrl=https://server1.[redacted].ux.internal.cloudapp.net:6443/arcgis/admin/info &token=jDVMyT9_nFo4CqCPyZ_K06FXaMqtb2KTfxYoMXp9xBxU50dIMCvoEel_sOLAL4wfJHhhVQFLxeZGszCUwy-J8OiyvhGPbV-KTb0b50ucum0nymjuwVw5LrS-w3ZWcjjPPJGIIiWK98fYjnCP0KOl4IulL7OJBsiwDO0LE2aLJq_5wVs4Ry6npKXdumvCD_B3I4NSNhulOy-ZXElYzv8XBvKiJiBBLX613CoTWGkakJI. &referer=server1.[redacted].ux.internal.cloudapp.net:6443&f=json &callback=dojo_request_script_callbacks.dojo_request_script10
responds with code 200, but the response payload is:
dojo_request_script_callbacks.dojo_request_script10( { "error": { "code":400, "message":"Unable to generate token", "details":["Unable to generate token for this server"] } });
This call returns as expected for the original Server machine.
So, why can't I get a token for this new machine?
Hi Jonathan,
I think this may be an issue when you use port 6443 for the Administration URL during federation. It's recommended to use the Web Adaptor URL when you have a multimachine site:
Use step 11 in the doc below to update the admin URL:
Thanks Jake Skinner and Jonathan Quinn for your responses.
Now, I can't access the server manager using the local address from either server machine -- both machines now get stuck on "Please Wait...". Which is fine, I suppose, but is the implication that multi-machine ArcGIS Server site that's federated with Portal can only be administered through the Web Adaptor?