Registry

Define registries and access scoping for projects in JFrog Connect.

When you use JFrog Connect to deploy software to edge or IoT devices, the Connect Agent pulls the software image from a designated registry (such as JFrog Registry, Git, or DockerHub) where the image is stored.

When you use Connect for the first time, one JFrog registry is already configured in Artifactory. Before you can use this registry, you have to define the access scoping. For any additional JFrog registries that you create, you will follow a simple two-step process:

  1. Add the JFrog registry.

  2. Configure Artifactory Access Scoping for that registry.

This process ensures that you have proper access controls in place for effective management of your software deployment.

Additional Registries

To define registries in addition to the default registry, use the procedures as indicated below. Registries that are not JFrog do not include access scoping.

Registry
See…

Additional JFrog registries (Artifactory)

Artifactory Edge

Private Git

Private Docker Registry with providers AWS ECR, DockHub, or private

What’s Next?

Learn how to add an Artifactory Access Scope to your first JFrog registry and to additional JFrog registries.

Last updated

Was this helpful?