Skip to content

Secrets Storage, Handling and Redaction #5

@JoTurk

Description

@JoTurk

Ensure secrets (TURN creds, database creds, tokens) are never logged and can be sourced securely.

Options & Discussion

  1. File paths for secrets
  • Pros: K8s/Container friendly
  • Cons: More IO wiring
  1. Env only
  • Pros: Simple
  • Cons: Risk of exposure

Sub-issues / Tasks

  • encourage users to store secrets in hashed or encrypted forms when appropriate, e.g: TURN tokens.
  • Allow reading secrets from file paths or env

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions