@ ArcGIS Server & Portal For ArcGIS

[NandhiniDevi]

Hi all,

We have a problem here, We have config the arcgis server and portal for arcgis in a single machine. Where portal for arcgis is config with web adaptar in http 80 port & https 443 and Arcgis server manager is config with web adaptar in http 81 port & https 447. Since when we assigned the domain name we made reverse proxy for the Portal for arcgis in Port 81. Both Portal for arcgis & Server manager works good. But the rest services we published in Server can't be accessed in the Portal for arcgis web map when add via the ArcGIS Server web service. 

Throws the following error -

Unable to access the authentication service

#Arcgis server & Portal for arcgis.

Thanks...

[TrevorNickolai]

Hello Nandhini,

When we get a secondary login request when accessing content within Portal, this can typically mean that the federation between Portal and ArcGIS Server is using a different PortalURL than what we are using to access the Portal itself.  Could you please verify the Portal URL you are currently using to access the Portal Map Viewer?  If you access ArcGIS Server admin api login page, you should see a PortalURL listed underneath were you login.  Is this URL identical to the first PortalURL?

[NandhiniDevi]

Hi Nickolai,

Thanks. Yes both URL Identical. Sorry I was not sure about this ArcGIS Javascript API. I am thinking may be the issues is right here. When I tried to login with the ArcGIS Server Rest API login after changing the domain name I am getting the 500 error. Initially before changing the domain name and installing the SSL certificate  we are able to login and use the services with rest endpoint api but now we are not able to access it.

When I use the domain name and try to access the ArcGIS Server REST API Login-

Appreciated for your quick responses.

[BillBott]

That's an IIS error, doesn't know how or can't route the request. Double check the port bindings - http to 81, https to 447 and the cert for 447 is the same as the one for 443. Next, either disable the firewall or add custom rules for opening the non-standard ports. For testing, I would turn off the firewall get it working then turn back on and add custom rules later. 

Was still curious why you choose non-standard ports and it's a lot of extra work not just to set up, but for clients to use and remember. The only reason I could think is that maybe you're trying to hide the ports? Even then they could be discovered with a simple port scan.

IIS can handle multiple requests for different web adaptors on the same standard ports (80/443).

[TrevorNickolai]

Good Morning Nandhini,

I see you mentioned you changed the domain name.  There is a lot of extra information needed to be able to properly diagnose this issue.  If possible, I would suggest having a case created for further support as I wouldn't want you sharing certain information on GeoNet.

[BillBott]

Would advise running them both on same standard ports, what’s the reason for going custom ports?

[Christopher28]

That's a good question. It's not necessary to do that and I think that's the cause of the problem.

[BlakeBilbo]

Hello, Nandhini Devi

This Blake Bilbo, the Head of Support for GEO Jobe GIS Consulting, and our family of products, including Admin Tools for ArcGIS. This scenario touches on a point that many organizations may run into for their ArcGIS Server & Portal For ArcGIS.

Please check out this blog article from an expert in our Enterprise team:

Don’t Go Rogue with Your Enterprise Deployment

[JonathanQuinn]

Non-standard ports are supported starting at 10.6.1:

Ex.

Use nondefault ports for the portal's ArcGIS Web Adaptor—Portal for ArcGIS (10.6) | ArcGIS Enterpris... 

If you're on 10.6 or earlier, then non-standard ports are likely the problem. If you are at 10.6.1, then make sure you're following the instructions in the link above. I think the information assumes that you have a reverse proxy running on 80/443, and the software may be assuming standard ports as well. As Bill Bott‌ suggests, start with using standard ports and go from there. Reconfiguring the public URLs of the deployment does require a bit of work though. It's best to reach out to Tech Support to understand what's involved and if it's necessary to rebuild.