Add Artifactory Access Scope
Add an access scoping in JFrog Connect.
Access scoping in JFrog Connect is a method of ensuring that only the intended artifacts are distributed to the intended devices. This is a way of protecting both the artifacts and the devices from unauthorized or inappropriate distribution.
Access scoping enables you to define and restrict artifact distribution based on specified fleet configurations and Artifactory sources. For example, to configure a complete access scoping, you will associate one or more device fleets to the following elements:
Registry: A JFrog server URL, which accesses either an Artifactory registry or an Artifactory Edge server.
Artifactory Project: A Project in Artifactory from which content will be allowed. You can allow multiple Artifactory projects.
Environment: A set of resources that are mapped to an Artifactory Project for a specific purpose, for example, Development, Testing, Staging, Production. Multiple environments can be mapped to a single Artifactory project.
Prerequisites
Administrator role
At least one registry, one Artifactory project, and one environment created in Artifactory
At least one fleet defined in Connect
Configure an Access Scope
To create an access scope, do the following:
In General Settings, go to the Registry Management tab and choose JFrog for the Registry Type.
Locate the relevant registry in the table and click anywhere in the row. The JFrog Registry Scope panel will appear on the right.
Tip: If you first need to create a new registry, click Add Registry in the top right of the Registry Type page and complete the procedure in Add JFrog Registry.
At the top of the panel on the right, click Add Scope. In the Add Artifactory Scope popup, choose an Artifactory Project, an Environment, and one or more Fleets. If you choose multiple Artifactory projects, then Environment will automatically be set to All.
Usage Rules
If you choose multiple Artifactory Projects, the value for Environment will automatically be All.
If you want to select less than All environments, you can select only one Artifactory Project.
If the registry you chose in Step 2 was of sub-type Edge, then you can choose only from the Fleets in the scope. Artifactory Project and Environment will automatically be All and All.
If the registry you chose in Step 2 was of sub-type Edge, then you can have only one Scope defined in the Scopes table.
If you are using the Docker Compose or Debian Package actions in your update flow, Artifactory Project and Environment must be set to All.
Whenever you choose All, this means all current and future items. This is true for Artifactory Projects, Environments, and Fleets.
Click Save and your scoping configuration is complete.
To close the loop entirely, ensure that your user (or user role) definitions include access to the correct Fleets.
What’s Next?
Learn how to add a JFrog registry to Connect.
Last updated
Was this helpful?