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
docs: add ARC_AUTH_BOOTSTRAP_TOKEN and ARC_AUTH_FORCE_BOOTSTRAP (v26.04.1)
- Add bootstrap_token and force_bootstrap to Arc and Arc Enterprise
auth config reference and docker env var tables
- Add Bootstrap & Recovery section to authentication guide with
usage examples and "Available since v26.04.1" admonition
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
bootstrap_token = ""# Pre-set admin token value (v26.04.1+)
396
+
force_bootstrap = false# Add a recovery token without removing existing ones (v26.04.1+)
395
397
```
396
398
399
+
:::info Available since v26.04.1
400
+
**`bootstrap_token`** — Set a known admin token at deploy time via `ARC_AUTH_BOOTSTRAP_TOKEN` instead of catching a randomly generated one from startup logs. On first run, Arc uses this value as the initial admin token. On subsequent restarts, it is a no-op.
401
+
402
+
**`force_bootstrap`** — Recovery path when the admin token is lost. Set `ARC_AUTH_FORCE_BOOTSTRAP=true` alongside `ARC_AUTH_BOOTSTRAP_TOKEN` to add a new `arc-recovery` admin token **without removing existing tokens**. Remove this flag after recovery. See the [Authentication configuration guide](/docs/configuration/authentication#bootstrap--recovery) for full details.
`ARC_AUTH_BOOTSTRAP_TOKEN` and `ARC_AUTH_FORCE_BOOTSTRAP` are available in Arc and Arc Enterprise v26.04.1 and later.
69
+
:::
70
+
71
+
### Pre-configured Bootstrap Token
72
+
73
+
By default, Arc generates a random admin token on first start and prints it once to stderr. If you miss it, recovery requires deleting the auth database and redeploying.
74
+
75
+
`ARC_AUTH_BOOTSTRAP_TOKEN` lets you set a known token value at deploy time. On first run, Arc uses this value as the initial admin token instead of generating a random one. On subsequent restarts, it is a no-op — the existing token is preserved.
-**Automated deployments** — bake the token into your secrets manager (Vault, AWS Secrets Manager, Kubernetes Secrets) and have it ready without catching a log line
83
+
-**Reproducible environments** — staging and production can use different known tokens set consistently at deploy time
84
+
85
+
:::caution Minimum length
86
+
Token values must be at least 32 characters. Values are stored as bcrypt hashes — the plaintext never persists to disk.
87
+
:::
88
+
89
+
### Recovery When the Admin Token is Lost
90
+
91
+
If you no longer have access to any admin token, set both `ARC_AUTH_BOOTSTRAP_TOKEN` and `ARC_AUTH_FORCE_BOOTSTRAP=true` before restarting Arc. Arc will add a new admin token named `arc-recovery`**without removing any existing tokens**.
Existing tokens are preserved so that if the recovery token was injected by a bad actor, any legitimate admin still has their token and can revoke it immediately via the API.
99
+
100
+
After recovering access:
101
+
1. Use the API to review and revoke any tokens you no longer need
102
+
2. Remove `ARC_AUTH_FORCE_BOOTSTRAP` from your deployment configuration
103
+
104
+
:::tip Idempotent on restart
105
+
If Arc restarts with `ARC_AUTH_FORCE_BOOTSTRAP=true` and the `arc-recovery` token already exists, it is a no-op. You still hold the token value you provided.
106
+
:::
107
+
61
108
## Token Management
62
109
63
110
All token management endpoints require **admin** authentication.
0 commit comments