Skip to content

Commit 9f82771

Browse files
committed
docs(spec): keep the handleInboundHook signature-form text as merged
The accepted signature forms are outside this change. The verification bullet keeps its merged wording and only hands a missing or wrong signature to the one unverified-post refusal. Claude-Session: https://claude.ai/code/session_01CBAfsWMSfM3EToQGVStEcp Co-authored-by: Claude <noreply@anthropic.com>
1 parent f26b2f4 commit 9f82771

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎packages/spec/src/contracts/trigger-api-service.ts‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ export interface ITriggerApiService {
5454
* id gets this `503`, signed or not. It stays a `503` on purpose: it is
5555
* the deployment's fault, a sender retries it, and it lasts only while
5656
* the secret cannot be read.
57-
* - It verifies the `x-objectstack-signature` header over the raw body
58-
* under that secret, through `@objectstack/core`'s `verifyHttpSignature`,
59-
* the one definition of the forms a sender may sign with.
57+
* - It verifies the `x-objectstack-signature` header (`sha256=` and the hex
58+
* HMAC-SHA256 of the raw body under that secret). A missing or wrong
59+
* signature gets the unverified-post refusal below.
6060
* - **One refusal for every post that does not verify** (#22806): an
6161
* unknown flow, a wrong hook id, an absent signature and a bad one all
6262
* answer `401 INVALID_SIGNATURE`, with one body. So the answer does not

0 commit comments

Comments
 (0)