Skip to content

Add support for password authentication #32

Open

Description

@AlexJuca

Context

FKVS currently has no authentication. Before production exposure, clients need an authentication mechanism so unauthenticated users cannot read, write, delete, or inspect server data.

Related: #33 covers TLS, and #77 covers safe network exposure and limits.

Scope

  • Add configurable password/token authentication.
  • Define an AUTH command or connection-level authentication flow.
  • Reject all protected commands until authentication succeeds.
  • Avoid logging secrets.
  • Support secret loading from config and, ideally, environment variables or secret files.
  • Consider separate permissions later, but start with a single shared secret if that is the pragmatic first step.

Acceptance criteria

  • Unauthenticated clients cannot execute data or admin commands.
  • Authenticated clients can execute commands normally.
  • Failed auth attempts are counted and logged safely.
  • Tests cover unauthenticated access, successful auth, failed auth, and reconnection behavior.
  • Docs explain secure configuration and secret handling.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions