Authorize remote modules with bearer proofs
This commit is contained in:
parent
72cd018a3e
commit
7e39a19c18
8 changed files with 572 additions and 120 deletions
|
|
@ -223,8 +223,12 @@ resource-scoped capability decisions.
|
|||
- `[x]` `geth secret bearer challenge/prove/verify` exercises
|
||||
resource-scoped bearer challenge-response proofs.
|
||||
- `[x]` Tests verify valid bearer proofs and capability-scoped proof denial.
|
||||
- `[ ]` Future completion wires bearer proof verification into remote module
|
||||
authorization paths.
|
||||
- `[x]` Remote module authorization paths accept optional bearer proofs for
|
||||
the requested resource capability without granting node identity.
|
||||
- `[x]` Tests verify remote CAS fetch succeeds through a bearer proof before
|
||||
the caller has a node grant.
|
||||
- `[ ]` Future completion avoids sending bearer secret identifiers as proof
|
||||
material by separating public bearer ids from private bearer tokens.
|
||||
|
||||
- `[~]` SSH certificate and revocation lifecycle.
|
||||
Acceptance criteria:
|
||||
|
|
|
|||
Loading…
Reference in a new issue