Multi Site Limitations

Limitations

With the Multi Site architecture, JFrog federation features have some limitations to be aware of

• For federation to work, all JFrog Platform sites need to be able to reach each other over https. Without a bi-directional access, the federation will fail
• When federation is enabled, it is very much impacted by network latency, so need to allow time for a package in a the source federated repository to be visible in the remote target site’s repository
• Currently, only Access and Repository federation are supported. Objects outside of these two are not federated, and should be managed individually per each JFrog Platform site (like Projects, Repositories and Xray policies). JFrog plans to expand the Federation capabilities to the whole platform
  • Features not covered by federation capabilities yet need to be configured separately on each site
• It’s recommended to use IaC tools like Terraform and harness the JFrog Terraform Providers to manage your platform’s configuration