docs: refresh control-ui shared-secret mirrors

This commit is contained in:
Peter Steinberger
2026-04-04 21:05:12 +01:00
parent 90387d4a88
commit 0738ed8d19
3 changed files with 10 additions and 4 deletions

View File

@@ -225,7 +225,8 @@ For the generic Docker flow, see [Docker](/install/docker).
`http://127.0.0.1:18789/`
Paste your gateway token.
Paste the configured shared secret. This guide uses the gateway token by
default; if you switched to password auth, use that password instead.
</Step>
</Steps>

View File

@@ -31,7 +31,8 @@ kubectl port-forward svc/openclaw 18789:18789 -n openclaw
open http://localhost:18789
```
Retrieve the gateway token and paste it into the Control UI:
Retrieve the configured shared secret for the Control UI. This deploy script
creates a gateway token by default:
```bash
kubectl get secret openclaw-secrets -n openclaw -o jsonpath='{.data.OPENCLAW_GATEWAY_TOKEN}' | base64 -d

View File

@@ -29,8 +29,12 @@ Auth is supplied during the WebSocket handshake via:
- `connect.params.auth.password`
- Tailscale Serve identity headers when `gateway.auth.allowTailscale: true`
- trusted-proxy identity headers when `gateway.auth.mode: "trusted-proxy"`
The dashboard settings panel keeps a token for the current browser tab session and selected gateway URL; passwords are not persisted.
Onboarding generates a gateway token by default, so shared-secret setups usually paste that here on first connect.
The dashboard settings panel keeps a token for the current browser tab session
and selected gateway URL; passwords are not persisted. Onboarding generates a
gateway token by default, so shared-secret setups usually paste that token here
on first connect, but password auth works too when `gateway.auth.mode` is
`"password"`.
## Device pairing (first connection)