Skip to content

feat(openclaw): Ed25519 device auth for full scoped gateway access#462

Open
Steven17D wants to merge 1 commit intoasheshgoplani:mainfrom
Steven17D:fix/openclaw-token-auth
Open

feat(openclaw): Ed25519 device auth for full scoped gateway access#462
Steven17D wants to merge 1 commit intoasheshgoplani:mainfrom
Steven17D:fix/openclaw-token-auth

Conversation

@Steven17D
Copy link
Copy Markdown
Contributor

Summary

  • Adds Ed25519 device identity and pairing flow for OpenClaw gateway authentication
  • New agent-deck openclaw pair command for device registration
  • Replaces simple password auth with scoped token-based auth using device keypairs
  • Stores device tokens locally for persistent authentication

Test plan

  • Run agent-deck openclaw pair, verify device identity is created
  • Test agent-deck openclaw pair --id shows device ID
  • Verify gateway connection with device auth after pairing
  • Test re-pairing and token refresh flows

🤖 Generated with Claude Code

The OpenClaw gateway strips operator scopes from connections without
cryptographic device identity. This adds proper Ed25519 device
authentication to the OpenClaw client:

- Generate and persist Ed25519 keypair (~/.agent-deck/openclaw/device.json)
- Derive deviceId from SHA256(raw_public_key)
- Sign v3 auth payloads (deviceId|clientId|mode|role|scopes|ts|token|nonce|platform|family)
- Include signed device identity in every connect handshake
- Persist device tokens from hello-ok responses
- Request all operator scopes (admin, read, write, approvals, pairing)
- Send auth token in both token and password fields
- Add `agent-deck openclaw pair` command for explicit pairing workflow
@Steven17D Steven17D force-pushed the fix/openclaw-token-auth branch from b2bdefc to 1569a90 Compare March 30, 2026 02:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant