There is no self-service “forgot password” flow in v1.
How Admin credentials are stored
Local users are stored as Kubernetes Secrets namedfalkordb-user-<sanitized-email> in the admin server namespace. The email is lowercased and any character outside a-z0-9- is replaced with - (for example admin@example.com becomes falkordb-user-admin-example-com). Each Secret has a user key containing a base64-encoded JSON document with a bcrypt password hash.
Note: re-running helm upgrade with a new adminServer.bootstrap.adminUser.password does not reset the password — the chart preserves an existing user Secret. You must patch the Secret directly.
Reset the password in the Kubernetes Secret
-
Find the admin user Secret:
-
Generate a bcrypt hash for the new password:
Or with Node.js:
-
Patch the
userJSON in the Secret with the new hash and force a password change on next login: -
Log in with the new password. You are prompted to change it immediately (
mustChangePasswordis set).
DISABLE_LOCAL_AUTH=true on the admin server), re-enable local auth temporarily via adminServer.env before resetting, then disable it again afterwards.
Resetting other users’ passwords
If an admin can log in, reset other users’ passwords through the product instead of touching Secrets:-
Admin UI: open Users, select the user, select Reset Password, and share the temporary password through a secure channel. Requires
users:updatepermission. -
CLI:
-
API:
mustChangePassword: true, and returns it in the response:
Notes
- Resets performed through the API are recorded in the audit log as
user.password_change. Direct Secret edits are not audited, so record them in your change management process. - Bootstrap values reference:
adminServer.bootstrap.adminUser.*in Helm values.