Summary
Access Federation setup fails when Mission Control cannot resolve the target JPD to a single record. The lookup matches on the Access service ID or the Custom Base URL. When that lookup returns more than one JPD, Mission Control throws a “There cannot be several matches” error.
The Platform UI may then show Cannot read properties of undefined (reading 'data'). That message is the UI reaction to the failed Mission Control call. The backend exception is the error to diagnose.
Symptoms
Access Federation setup fails in Administration > User Management > Access Federation.
The UI shows Cannot read properties of undefined (reading 'data') or a generic failure.
$JFROG_HOME/artifactory/var/log/mc-error.log contains:
java.lang.IllegalStateException: There cannot be several matches
at org.jfrog.mc.jdbc.repositories.FederalizableJpdRepositoryFacade.optionalOfSingletonList
at
org.jfrog.mc.jdbc.repositories.FederalizableJpdRepositoryFacade.findByAccessServiceIdOrCustomJpdUrlThe same exception can appear as Could not get configuration from <JPD name>: There cannot be several matches.
Diagnosis
Run these checks on every JPD involved in the federation, including all HA nodes.
-
Compare the Custom Base URL
curl -u admin:<password> \
"https://<jpd-base-url>/artifactory/api/system/configuration/platform/baseUrl"
Each physical JPD must return its own URL. Both nodes of one HA cluster must return that cluster's URL. In the UI, the same value is under Administration > Artifactory > General Settings > Custom Base URL.
For geo-load balancing that intentionally shares a Base URL, the reverse proxy can send a distinct identity with the X-JFrog-Override-Base-URL header. Each JPD still needs a unique value in Mission Control.
-
Collect the Access service ID
curl -u admin:<password> \
"https://<jpd-base-url>/router/api/v1/system/health"
Use the object whose service_id starts with jfac@:
{
"service_id": "jfac@<access-service-id>",
"node_id": "<node-id>",
"state": "HEALTHY"
}-
Inspect the outbound Access configuration
Verify $JFROG_HOME/artifactory/var/etc/access/access.config.latest.yml on each JPD:
federation:
outbound:
servers:
- name: "jfac@<access-service-id-of-the-other-jpd>"
url: "https://<other-jpd-base-url>/access"A correct entry has both of these properties:
Resolution
-
Each JPD should have a distinct Custom Base URL.
-
Verify the outbound server on each JPD, so the name is the remote jfac@ ID, and the URL is https://<remote-base-url>/access.
-
Remove the affected JPD from Administration > Platform Deployments > Registered JPDs, then register it again with the unique URL and a new pairing token.
-
Verify and reconfigure the Circle of Trust in both directions.
-
Apply the Access Federation topology again.