Account Security
Enforce two-factor authentication (2FA) and session expiration for email/password accounts, and recover locked-out users from the command line.
Two-factor authentication and organization session policies are enterprise features. See Pricing Model.
Two-Factor Authentication
Members enroll under Personal Settings → Sign-in & security → Two-factor authentication and keep their backup codes.
Organization-Wide 2FA Enforcement
With organizationSettings:update, require password-authenticated members to enroll before using Archestra:
- Go to Settings → Auth.
- Turn on Require Two-Factor Authentication.
When turned on:
- Members without 2FA enrolled are signed out immediately across all replicas.
- On next sign-in, members must complete 2FA enrollment before accessing any API or page.
- The Settings → Users table adds a 2FA column showing member enrollment status.
Deployments with password authentication disabled (ARCHESTRA_AUTH_DISABLE_BASIC_AUTH=true) cannot enforce in-app 2FA. Enforce multi-factor authentication directly at your identity provider instead.
Session Lifetime Caps
Set a maximum session age to require sign-in again even for active users. Changing it requires organizationSettings:update.
- Go to Settings → Auth.
- Under Maximum session lifetime, select a duration preset or enter a custom duration.
Once a session exceeds this age from sign-in, Archestra revokes the session and redirects the user to sign in again. Rotating ARCHESTRA_ immediately invalidates all active sessions; see Session Secret.
Reset a Password from the CLI
A reset invalidates existing sessions and records a password-reset event in the audit log.
Helm or Kubernetes
Run the reset script inside the platform deployment pod:
kubectl exec -it deploy/archestra-platform -- \
sh -c 'cd /app/backend && node dist/standalone-scripts/reset-user-password.mjs --email user@example.com'
Docker Quickstart
Pass the database connection URL into the container command:
docker exec -it <container> sh -c 'cd /app/backend && \
ARCHESTRA_DATABASE_URL=postgresql://user:password@localhost:5432/database \
node dist/standalone-scripts/reset-user-password.mjs --email user@example.com'
Script Flags
| Flag | Description |
|---|---|
--email <email> | Required. Target user email. |
--password <password> | New password (8–128 characters). If omitted, generates and prints a random password once. |
--disable-two-factor | Clears the user's 2FA enrollment so they can sign in after losing an authenticator device. |
--help | Display command usage. |
Recovering a Locked-Out Admin
If SSO fails while password authentication is disabled (ARCHESTRA_AUTH_DISABLE_BASIC_AUTH=true), restore access from the cluster:
- Reset an administrator account password using the CLI script above.
- In the backend environment, unset
ARCHESTRA_and restart the pod or container.AUTH_ DISABLE_ BASIC_ AUTH - Sign in with the temporary password and correct the SSO identity provider settings.
- Re-enable
ARCHESTRA_AUTH_DISABLE_BASIC_AUTH=trueonce verified.