Module: Artifact Registry — Upstream Proxy

Registry type affected: npm

Problem: The current upstream proxy only supports Basic authentication or anonymous access. npm's registry API (https://registry.npmjs.org/) requires Authorization: Bearer <token> for authenticated requests. Basic auth returns 401.

Impact: Private scoped packages (e.g., @payloadcms/*) cannot be resolved through a Harness npm upstream proxy.

Root cause: npm permanently revoked classic tokens in December 2025; only granular access tokens sent as Bearer tokens are supported.

Requested feature: Either:

A native Bearer token authentication type for upstream proxies, with the token stored in Harness Secret Manager, or

A custom static Authorization header per upstream proxy, sourced from Harness Secret Manager.