You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity