You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: Optional Security Headers added for webhook outputs (#379)
* feat: Optional Security Headers added for webhook outputs
- optional security header can be enabled by adding the following to your config:
-"webhookHmacSharedKey": "SomeRandomHMACKey"
(Replace "SomeRandomHMACKey" with your private HMAC secret key)
- when ENABLED, the following headers will be included in the webhook
request:
x-hmac-time 1747750828
x-hmac-signature 7420964e60045e716a9b1d4fabcbc6a9cc913c7e63ac653b313d56a097a36d1a
x-request-id 769164d0-5592-4a67-9932-038573732fdc
(example values shown)
--
NOTE:
- THIS MUST USE **SHA-256** HASHING ALG
- MESSAGE TO HASH is **x-hmac-time + x-request-id** (UTF-8 string, no
seperators)
- DIGEST OUTPUT is **HEX STRING**
- x-hmac-time is **UNIX EPOCH TIME**
- signature is computed using your shared **`webhookHmacSharedKey`**
- You MUST validate that the timestamp is within an acceptable range
(e.g. 5 minutes) *before* comparing the HMAC (do this on your backend)
* Update statusService.ts
remove redudant code.
* Update types.ts
made webhookHmacSharedKey optional
0 commit comments