Portal and Reverse Proxy: Too Many Redirect Errors
Hello,
I have not been able to find step by step directions for ArcGIS for Portal and Reverse Proxy which uses IIS as a server. I have a setup in place which mostly work but fails at one critical point. Here's the setup:
1) Reverse Proxy Server (Windows) with static IP address accessible from the outside (only ports 80/443 allowed in).
2) An internal machine ('GIS') which has ArcGIS for Portal and Server installed along with their respective Web Adaptors ('portal' and 'arcgis' respectively).
3) The Portal also has WebContextURL of like 'https://gis.mydomain.com/portal'
4) The RP server has a couple of URL Rewrite entries--basically, direct to Server Farm which has the 'GIS' machine.
5) A proper SSL certificate is install as gis.mydomain.com in the IIS of both the RP server and the 'GIS' server.
So far this setup works great: I am able to access all content from the outside, such as https://gis.mydomain.com/portal/home and Gallery etc. But clicking on the Signup link in the Portal home page generates a browser error: Too Many Redirects (Header of 302). So the header being passed backed from the internal machine is 302 instead of 200.
I don't know what's happening. Maybe some extra security comes in picture when the signup.html page is called?
Any idea?
Thanks!
Irfan
*** Update: Reverse Proxy Rules Screen Cap Added in this Question***
I think we'd rely on the vendor of the load balancer to provide necessary documentation on configuring it before we put it in our documentation as they are more familiar with how to configure their own products. If there's something that our software expects, (for example, setting the Web Context URL for Portal and Server or what headers should be included in any request), then we do our best to document those steps or information. In response to your numbered points:
1) I set the WebContextURL in the Portal and Server's Administrator Directory (from the links above):
Portal
Server
It isn't always necessary to set the privatePortalURL for Portal. You'd only use it if you are setting up an HA Portal or Server can't communicate directly with the Portal over 7443.
2) SSL Certificates likely won't cause a redirect. They have to be installed on any IIS instance which includes the reverse proxy and the IIS instance hosting the web adaptors. They are certificates from our domain signing authority. Even if they were self-signed certificates, they shouldn't cause redirects, only certificate warnings. I'm not sure of the behavior if the reverse proxy machine doesn't trust the certificate that is used for the Web Adaptor machine, so that's definitely something to look into. This can be checked by navigating to the Portal or Server through the Web Adaptor URL.
3) Again, I would refer to the vendors documentation on URL Rewrite rules and Server Farm configurations as it's technically a third party component and not directly supportable. There are a number of blogs on the URL Rewrite module:
URL Rewrite : The Official Microsoft IIS Site
Setting HTTP request headers and IIS server variables | Microsoft Docs
Modifying HTTP Response Headers | Microsoft Docs
The documentation on the Windows site will be far more detailed and will likely be kept up to date more accurately than information we transpose to our documentation.
If it turns out there was a setting or configuration that was necessary to make things work in your environment, then we can consider adding that as a general note, but not include within a larger step by step guide.
In my configuration, I didn't make any changes other than adding the machine to a new Server Farm. I left everything else default.
