[RTFACT-16130] In some cases Access to Access in HA will not work with Tomcat and/or Network (reverse proxies) configurations Created: 15/Mar/18 Updated: 28/Aug/18
|Project:||Artifactory Binary Repository|
|Component/s:||Access Server, HA, Reverse Proxy Configuration Generator|
emphasized textGoing from 5.6.0, Access runs on its own connector and/or can be access via Artifactory connector with the /access context.
This can cause issues when:
1. A reverse proxy is used behind each Artifactory node, a the context.url (under ha-node.properties) could, and is, binded to the Reverse proxy (e.g. Nginx) Virtualhost/listener port; e.g.:
And, since by default, Artifactory's snippet generator is not taking care of the access servlet.
This can be handled by adding another directive that would make the reverse proxy forward requests to the Access context, e.g. with Nginx use the location directive for /access/ (same as /artifactory/):
2. Artifactory runs on the ROOT virtual listener of Tomcat:
|Comment by Ariel Kabov [ 30/Apr/18 ]|
This issue seems to also affect whoever configures Artifactory to run as ROOT on Tomcat:
In this case, the workaround is to use this special Artifactory ha-node.properties property: