Skip to main content

Multi-Site Limitations


Overview

Several federation services can connect sites. They do not sync the same objects, and they do not all run the same way on every hosting model. Platform Federation is the recommended way to keep the platform configuration in sync.

Platform Federation

  • Syncs Projects, members, roles, stages, users, groups, permission targets, access tokens, and policies. On JFrog SaaS it also provisions repositories. On self-managed, repository provisioning is a future release
  • Available on Enterprise+. Self-managed Platform Federation is in early access. Hybrid membership, a SaaS site together with self-managed sites, is planned
  • Member sites are a mesh of peers. Star and chained topologies are not supported, and there is no filter for which entities sync
  • Artifactory Edge nodes cannot join. Sync Access entities on an edge with Access Federation

Repository federation and Access Federation

  • Repository federation syncs artifacts and metadata. Platform Federation uses it for the local repositories it provisions, and it also keeps working on its own
  • Access Federation syncs users, groups, and permissions on edges, in star or chained topologies, and between sites that are not in a Platform Federation. It can filter and map entities. Platform Federation cannot
  • Those services need the sites to reach each other over HTTPS in both directions. One-way access fails the federation
  • Network latency delays how soon a package in a federated repository is visible on the other site
  • Xray, Distribution, and other objects outside these services are configured on each site. JFrog plans to expand federation to the whole platform. Use Terraform and the JFrog Terraform Providers for configuration that is not federated yet