Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Artifact RegistryAuthentication

Set registry visibility

Set a registry to Private so only authenticated users can access it, or to Public so anyone can pull artifacts without authentication.

Every registry in Harness Artifacts has a visibility setting that controls who can view its contents and pull from it.

  • Private: only users and service accounts with the required permissions or a valid identity token can view the registry and pull artifacts.

  • Public: anyone can view the registry contents and pull artifacts without authentication. Pushes still require authentication regardless of visibility.

You can set visibility when you create a registry, or change it at any time from the registry's configuration.

Public visibility requires a feature flag

The Public option is gated by the PL_ALLOW_TO_SET_PUBLIC_ACCESS feature flag. If the option is missing, both of the following steps are required before it appears:

  1. Contact Harness Support to enable PL_ALLOW_TO_SET_PUBLIC_ACCESS on your account.

  2. In your Harness account, go to Account Settings > Authentication and turn on Allow public resources.

Set visibility on a new registry

Visibility is one of the fields on the Create a new artifact registry drawer. Select Private or Public before you click Create registry.

Go to Create a registry for the full creation walkthrough.

Change visibility on an existing registry

  1. In the left navigation, select Registries.

  2. Click the registry you want to update.

  3. Select the Configuration tab.

  4. In the Definition section, find the Visibility field and select Private or Public.

  5. The change saves automatically when you close the edit drawer.

Visibility and the Registries list

The Registries list shows a Visibility column for each registry. You can see at a glance which registries are public without opening each one.

Considerations

  • Making a private registry public means anyone with the registry URL can pull its artifacts. Review the contents before changing visibility.

  • Harness does not send a notification when registry visibility changes. Communicate the change to your team if downstream consumers rely on authentication.

  • Public visibility applies to pull operations only. Pushes always require a valid identity token, even for public registries.

Next steps

Last updated

Was this helpful?