Hello,
The environment is ArcGIS Enterprise 10.7.1 federated and distributed in 3 servers in Windows Server (Portal, ArcGIS GIS Server and DataStore), is running "normally" and are virtualized servers in VMware.
Tomcat and WebAdaptor were used to expose the environment, but due internal rules the organization it was decided not to use it and to expose it through a reverse proxy, Apache is used to manage the communication.
They have a rule like this.
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^TRACE
RewriteRule .* - [f]
RewriteCond %{REQUEST_METHOD} ^TRACK
RewriteRule .* - [f]
RewriteRule ^/portal$ https://public.dns.com/portal/
<Location “/portal”>
ProxyPass https://internal.server.domain:7443/arcgis
ProxyPassReverse https://internal.server.domain:7443/arcgis
Header set Access-Control-Allow-Origin “*”
</Location>
Almost the same conifguration for the ArcGIS GIS Server.
The access to Portal website is viable, you can log in, see the services (from ArcGIS GIS Server and hosted), view the viewers created before, creates new maps, WAB etc.
The issue its related to Portal, when it is required to access for example to Survey123 app, the ArcGIS Server manager to check the services etc (where it is required to generate security tokens) it returns the URL of the internal machine where the request was directed. This is problematic, as clients will not be able to access this URL. Also, this gives the client access to some information about the internal machine.
This is the same situation describe here.
Prepare your reverse proxy
https://enterprise.arcgis.com/en/web-adaptor/latest/install/iis/using-a-reverse-proxy-server-with-portal-for-arcgis.htm
The request starts from something like this (the correct url):
https://public.dns.com/portal/sharing/rest/oauth2/authorize?....
But it is redirected to the internal Portal server.
https://internal.server.domain:7443/portal/sharing/rest/oauth2/authorize?....
We can manually correct the url from internal.server.domain:7443 to public.dns.com and works fine, but this should be done by the reverse proxy.
We believe that its related to the value X-Forwarded-Host, that Apache do not have it; be we're not sure how configured, we have tried different configurations online and don’t work.
Have you seen this inconvenience before?
Regards.