Skip to main content

Client Setup

Last updated on
create a registry

If you haven’t created a registry yet, see create a registry.

Client Setup simplifies authentication and ensures proper configuration for different artifact types (e.g., container images, Helm charts). It also helps prevent common misconfigurations when pulling or pushing artifacts.

Client setup​

  1. Select Registries, then select a container register of type ARTIFACT REGISTRY, e.g. Docker or Maven.
  2. Select Set up client.
  3. Follow the on-screen instructions.

Configuration steps​

The Client Setup process provides step-by-step guidance, including:

  • Logging in to the registry.
  • Generating a password token.
  • Pulling an image or package.
  • Pushing an image or package.

Now, you should see the artifact appear in your docker registry as well as the Artifacts tab in the left navigation panel.

Authentication model​

Harness Artifact Registry uses token-based authentication (PAT or service account tokens). The pipeline identity model determines which permissions apply:

  • Manual triggers: The pipeline uses the triggering user's RBAC permissions.
  • Webhook, IDP (Internal Developer Portal), or schedule triggers: The pipeline runs as a service/bot principal and uses that bot's RBAC permissions.

This applies to both image pulls (requires read access) and the Upload Artifacts to HAR CI step (requires write access). If the triggering principal lacks the appropriate permission, the operation returns a 403 error.

Supported authentication methods

Harness Artifact Registry supports PAT (Personal Access Token) and service account tokens for authentication. These work across all deployment environments including EKS, GKE, and AKS.