Skip to content

Integrate Key Vault as a source for environment variable secrets #816

Description

@kriszyp

Request

Add Key Vault (Azure Key Vault, AWS Secrets Manager, HashiCorp Vault, etc.) as an option for sourcing environment variable secrets, complementing the hdb_env system table (CORE-2695). Operators could configure Harper to pull specific secrets directly from their existing vault at startup.

🤖 Filed by Claude on behalf of Kris.

Activity

  1. added
    enhancementNew feature or request
    from-jiraMigrated or originated from a Jira ticket
    area:authAuthentication, authorization, JWT, user management
    on May 27, 2026
  2. kriszyp commented on Jul 1, 2026

    @kriszyp
    MemberAuthor

    Folding this into the secrets-management plan: external key vaults slot in as custody providers behind the Pro KeyCustody seam (see harper-pro#166) rather than as a separate env-var source — same enc:v1: substrate, the vault just holds/unwraps the private key so it never enters the process. Scoped as part of the hardening phase after the store + file/injected providers land.

    🤖 Posted by Claude (Fable 5) on Kris's behalf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:authAuthentication, authorization, JWT, user managementenhancementNew feature or requestfrom-jiraMigrated or originated from a Jira ticket

Type

No type

Fields

Priority

P2

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions