Curation Federation

A Curation Federation replicates the repositories, conditions, labels, and policies you create on a controller site to follower sites. This enforces standardized governance rules across multiple JFrog Platform deployments while giving followers local flexibility where they need it.

Prerequisites

• Xray 3.143.x
• Artifactory 7.146.x
• Catalog requires running the ValKey installation

Federated Entities in a Curation Federation

The Curation Federation syncs the following entities:

• Remote Repositories – Connections created on the controller are propagated to all followers, ensuring consistent repository configurations.
• Conditions – Controller-defined conditions are federated as read-only on followers, while followers may create additional local conditions.
• Labels – Federated labels are available for use on followers in read-only mode, with the option for followers to add their own local labels.
• Policies – Policies defined on the controller can be applied organization-wide or by repository type, incorporating federated conditions and labels.

Federated Remote Repositories

When a remote repository of a specific type, such as npm, is connected to the controller, the connection is federated to all followers. Followers can't disconnect this federated connection. If a follower doesn't yet have that repository type, the configuration will be applied automatically if and when the repository is created.

Followers retain limited local control:

• They can exclude specific multi-site remote repositories via local settings.
• They can add new repository types that aren't configured on the controller. For example, if the controller doesn't configure a PyPI repository, a follower may configure one locally for its own use.

Federated Conditions

All conditions created on the controller are federated to followers. These federated conditions are read-only on follower sites and can't be modified.
Followers can, however, create their own local conditions. These are separate from the federated ones and aren't propagated back to the controller. Local conditions may still use read-only federated conditions as building blocks for policies.

Configure Curation Federation

Use this procedure to configure a Curation Federation.

Monitor Curation Federation

All curation and federation events are logged for review and troubleshooting:

• Controller Events: Show when federation started, what changes were applied, and which entities were affected.
• Follower Events: Show when changes were received and applied locally. Clicking on any event row will provide details such as when the federation started running on the controller and when it was received on the follower. This helps with gap analysis in case changes took a long time to propagate.