Issue Description
When setting up Access Federation between two Artifactory instances using the Access Federation workflow, in certain environments, the access microservice may fail to pick up this UI-defined Platform Default Proxy (Administration > Proxies). This results in connection failures accompanied by the following error in the logs:
Couldn't verify circle of trust with https://<art-url>/access
Cause
Access Federation traffic relies on the Access microservice. In specific configurations, the Access microservice does not automatically inherit or utilize the proxy configured via the Web UI (Platform Default Proxy). Explicit configuration inside the Access service settings file is required to direct traffic through the outgoing proxy.
Step 1: Backup the Existing Configuration
Before making any updates to system configuration files, create a backup of the current settings.
Navigate to the Access configuration directory on your On-Premises Artifactory node:
$JFROG_HOME/artifactory/var/etc/access/
Create a copy of access.config.latest.yml in a secure location outside or within the same directory:
cp access.config.latest.yml access.config.latest.yml.bak
Step 2: Update the Proxy Configuration
Explicitly define the proxy settings in the Access microservice configuration file.
-
Open $JFROG_HOME/artifactory/var/etc/access/access.config.latest.yml in a text editor.
-
Add the proxy block with your proxy details:
proxy:
host: "<YOUR_PROXY_HOST>"
port: <YOUR_PROXY_PORT>
(Replace <YOUR_PROXY_HOST> and <YOUR_PROXY_PORT> with your proxy server hostname and port number).
Step 3: Import and Apply Configuration Changes
To ensure Artifactory imports the modified YAML file upon startup, rename the configuration file and restart the service.
Rename access.config.latest.yml to access.config.import.yml:
mv access.config.latest.yml access.config.import.yml
Restart the Artifactory service to apply the configuration.
(If running a High Availability (HA) cluster, perform a rolling restart on all remaining cluster nodes to propagate configuration changes across the cluster.)