Abstract

A method is disclosed for driving an external signing and verification service over a JSON-RPC 2.0 tool-invocation protocol from a platform adapter holding a service credential, where the credential carries a request-supplied signer identity across the boundary only when that identity's identifier is on an allow-list the operator registered in configuration, and where only named counterparty members are admitted into platform responses. Before a state-changing signing call the adapter requires the request's signer descriptor to declare a human principal kind with a non-blank string identifier listed, by exact match, in that allow-list; an absent, empty or unparseable allow-list refuses every signing call. Both refusals precede credential resolution, client construction and any request. Failure envelopes from the remote service are rebuilt at the boundary: a string error member is kept, any other present, non-null error member becomes a malformed-error token, a fixed list of scalar diagnostics is kept and, on the two verbs that invoke the remote comparison, a fixed list of evidence members is kept as supplied; every other member is dropped. On those two verbs a failed envelope whose error member is absent or null means the comparison ran and did not pass: a negative verdict on the verification verb and a stable, evidence-bearing refusal token on the dry-run verb, while a failure carrying a non-null error member stays a refusal without a verdict. The transport client checks the protocol error member before the request-identifier echo, bounds the response size twice and resolves authentication headers per request.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS