Federated Repository Form Field Reference
Review every field on the Federated repository creation and edit form.
This reference documents every field in the Federated repository creation and edit form, organized by tab: Basic, Advanced, and Federation.
Who can perform these actions: Platform Administrators
Navigation: Administration > Repositories > Create a Repository > Federated (or click an existing Federated repository to edit).
Basic Tab
The Basic tab contains the repository identity, package-type-specific settings, and content filtering.
Common Fields for All Package Types
These fields apply to all package types.
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
| Package Type | Modal picker | (none) | Yes | The type of artifacts stored in this repository (Maven, Docker, npm, Generic, and others). Cannot be changed after creation. All package types are supported except TerraformBackend. |
| Repository Key | Text input | (empty) | Yes | Unique identifier for the repository. This key becomes the URL path segment and is replicated to all Federation members. Must be unique across the platform. When created inside a project, the project key is prepended automatically. |
| Repository Layout | Dropdown | Package-specific default | No | Defines the path structure for artifact resolution. Automatically set based on package type but can be overridden. Hidden for Release Bundles and Machine Learning package types. |
| Public Description | Text input | (empty) | No | User-visible description displayed in the Artifacts Browser. |
| Internal Description | Text input | (empty) | No | Admin-only description, not visible to non-admin users. |
| Includes Pattern | Multi-value pattern | **/* | No | Comma-separated Ant-style patterns for artifacts to include. Only matching artifacts are stored. Default **/* includes everything. |
| Excludes Pattern | Multi-value pattern | (empty) | No | Comma-separated Ant-style patterns for artifacts to exclude. Matching artifacts are rejected. Hidden for Build Info and Release Bundles. |
| Environments | Multi-select | (empty) | Project context only | Environment labels (DEV, PROD, and others) for project-scoped repositories. Required when the repository belongs to a project. |
Package-Specific Fields on the Basic Tab
These fields appear based on the selected package type.
Docker, HelmOCI, and OCI
These fields apply to Docker, HelmOCI, and OCI repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| Max Unique Tags | Number | 0 (unlimited) | Maximum number of unique tags to retain. Older tags are removed when the limit is exceeded. |
| Block Pushing Schema 1 | Toggle | false | (Docker only) Block Docker V1 schema images from being pushed. |
| Tag Retention | Number | 0 (unlimited) | Number of days after which unused tags are eligible for cleanup. |
| Registry Name | Text | (auto) | Docker registry name for this repository. |
| Registry Port | Number | (auto) | Docker registry port. Used for Docker V2 API compatibility. |
Maven, Gradle, Ivy, and SBT
These fields apply to Maven, Gradle, Ivy, and SBT repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| Handle Releases | Toggle | true | Allow release artifacts to be stored. |
| Handle Snapshots | Toggle | true | Allow snapshot artifacts to be stored. |
| Max Unique Snapshots | Number | 0 (unlimited) | Maximum number of unique snapshots to retain per artifact. |
| Suppress POM Consistency Checks | Toggle | false | Disable validation that POM coordinates match the deployment path. |
| Checksum Policy | Dropdown | client-checksums | How to handle artifact checksums: client-checksums, server-generated-checksums. |
| Snapshot Version Behavior | Dropdown | unique | How to handle snapshot version naming: unique, non-unique, deployer. |
NuGet
These fields apply to NuGet repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| Max Unique Snapshots | Number | 0 (unlimited) | Maximum NuGet snapshot versions to retain. |
| Force Authentication | Toggle | false | Require authentication for all NuGet operations, including package resolution. |
Debian and RPM
These fields apply to Debian and RPM (YUM) repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| GPG Key Pairs | Selector | (none) | GPG signing key pairs for signing Debian packages or RPM metadata. |
Alpine and Ansible
These fields apply to Alpine and Ansible repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| Key Pair | Selector | (none) | Signing key pair for package verification. |
Cargo
These fields apply to Cargo repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| Anonymous Access | Toggle | false | Allow anonymous download and search of Cargo crates. |
| Enable Sparse Index | Toggle | false | Enable the sparse index protocol for faster crate resolution. |
Terraform
These fields apply to Terraform repositories.
| Field | Type | Default | Description |
|---|---|---|---|
| Registry Type | Selector | (varies) | Terraform registry type (Provider or Module). Determines the repository layout. |
| GPG Key Pairs | Selector | (none) | GPG key pairs for Terraform provider signing (provider layout only). |
Advanced Tab
The Advanced tab contains proxy, property set, and operational settings.
Property Sets
You can associate property sets with the repository using this field.
| Field | Type | Default | Description |
|---|---|---|---|
| Property Sets | Transfer list | (empty) | Select property sets to associate with this repository. Property sets define structured metadata schemas that can be applied to artifacts. Move property sets between "Available" and "Selected" lists. |
Network
These fields configure the network proxy for Federation traffic.
| Field | Type | Default | Visibility | Description |
|---|---|---|---|---|
| Proxy | Dropdown | System default proxy | Self-hosted only | HTTP proxy to use for outbound Federation traffic to remote members. Select from configured proxies or leave as default. See Configure Proxy for Federation for setup steps. |
| No Proxy | Checkbox | false | Self-hosted only | Disable proxy usage for this repository. When checked, clears the proxy selection and uses direct connections. |
Note
Network proxy settings are hidden on SaaS deployments, as SaaS instances handle networking automatically.
Others
These fields control additional resolution and download behavior for the repository.
| Field | Type | Default | Visibility | Description |
|---|---|---|---|---|
| Disable Artifact Resolution | Checkbox | false | Always | When enabled, blocks all download and resolution requests. The repository still accepts deployments and replicates to Federation members. Useful for maintenance windows. |
| Allow Content Browsing | Checkbox | false | Always | Allow browsing of repository content via the Artifacts Browser even when artifact resolution is disabled. |
| Priority Resolution | Checkbox | false | Select packages | When enabled, this repository is prioritized during artifact resolution across virtual repositories. Available for specific package types only. |
| Enable Direct Cloud Storage Download | Checkbox | false | Self-hosted + cloud storage | Allow direct download from the underlying cloud storage (S3, GCS, Azure Blob), bypassing Artifactory for improved performance. Available only when using cloud-based binary storage. |
| Enable CDN Download | Checkbox | false | Enterprise license | Enable Content Delivery Network for artifact downloads, improving download speeds for geographically distributed teams. |
Federation Tab
The Federation tab manages the Federation members: the JPD instances that synchronize artifacts in this Federated repository.
Member Summary
This section shows how many Federation members are configured.
| Element | Description |
|---|---|
| Included Repositories (n/10) | Header showing the current number of Federation members out of the maximum 10. |
Member List
Each Federation member appears as a card with the following fields.
| Element | Type | Description |
|---|---|---|
| URL | Read-only text | The full URL of the Federated repository member (for example, https://jpd-site-b.example.com/artifactory/libs-release-federated). |
| Repository Key | Read-only text | The repository key on the remote JPD. |
| (current) | Badge | Indicates the member that corresponds to the local JPD. |
| Sync toggle | Switch | Pause or resume synchronization for this member. When paused, events queue locally but are not sent to this member. Only available on the current (local) member. Disabled when the member is in receiving-only mode. |
| Receiving Only | Checkbox | When checked, sets the member to receiving-only mode (receiver mirror mode). The member receives events from other members but does not send events. Only available for non-current (remote) members. See Configure Receiving-Only Mode for details. |
| Remove | Icon button | Remove this member from the Federation. Not available for the current (local) member. |
Adding Members
Use this control to add a new Federation member.
| Control | Description |
|---|---|
| Add Repository button | Opens the Add Federated Repositories dialog. Disabled if the repository key or package type is not set, or if the current member is in receiving-only mode. |
The Add Repositories dialog offers the following methods.
| Method | When Available | Description |
|---|---|---|
| Deployments | When JFrog Mission Control is available | Browse connected JPDs and select existing repositories or create new ones automatically. |
| URL | Always | Manually enter the full repository URL. If the repository does not exist on the remote JPD, it is created automatically. |
The URL must use the following format:
<BASE_URL>/artifactory/<REPOSITORY_KEY>Where:
<BASE_URL>: The base URL of the remote JPD, including scheme and host.<REPOSITORY_KEY>: The repository key on the remote JPD. Must be 64 characters or fewer and the URL must contain/artifactory/.
For example:
https://jpd-site-b.example.com/artifactory/libs-release-federatedNote
Remote JPDs appear in the Deployments list only if you have established binding tokens or a Circle of Trust between the JPDs.
Related Topics
Updated about 7 hours ago