ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-25 11:55:47 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs(gateway): correct node pairing storage (#124571)

Browse Source
This commit is contained in:
Peter Steinberger
2026-08-16 05:46:44 -07:00
committed by GitHub
parent ebd23631ae
commit eab287d224
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gateway/operator-scopes.md
+4 -4
View File
@@ -198,10 +198,10 @@ can approve, reject, rotate, revoke, or remove only its own device entry.
## Node pairing approvals
Legacy `node.pair.*` methods use a separate Gateway-owned node pairing store.
WS nodes use device pairing (`role: node`) instead, but the same approval
vocabulary applies. See [Gateway pairing](/gateway/pairing) for how the two
stores relate.
`node.pair.*` capability approvals are stored on the paired device record in
the shared SQLite pairing store. Gateways migrate any remaining entries from
the retired standalone `nodes/paired.json` store into those records once at
startup. See [Gateway pairing](/gateway/pairing) for details.
`node.pair.approve` derives extra required scopes from the pending request's
command list: