F
Fundamental Cod
Request: Provide a unified HAR authentication flow: one CLI login (using harness auth login --sso) stores a HAR-compatible user credential in the native OS credential store, and HAR config configures package-manager-specific integrations that reference that single credential.
Expected Behavior:
  • Reuse an active Harness browser session during login when security policy permits, avoiding redundant sign-in.
  • Store the credential in macOS Keychain, Windows Credential Manager, or Linux Secret Service, with no plaintext fallback.
  • Automatically configure supported credential integrations for pnpm, pip, Docker, and other package managers. Ordinary package-manager commands should work without token exports, plaintext credentials, or a CLI execution wrapper.
  • Allow developers to configure only the registries and package types they need, all referencing the shared credential.
  • Apply credential rotation across integrations. Removing a registry configuration must not delete the shared credential; explicit logout should remove it.
  • Preserve existing HAR permissions and clearly document package-manager limitations, including npm’s lack of a native credential-helper hook.
Benefit: One login enables secure, consistent access across permitted HAR registries, with minimal manual setup.