Files
zeekay 31a45e2826 Post a webhook as eSign only to a URL HANZO_WEBHOOKS lists exactly
A team chooses where its webhook points, so the origin was not enough: an admin
could aim eSign's identity at any Hanzo API route and read the answer in the
webhook log. One sender now serves sends and resends: a URL HANZO_WEBHOOKS
names exactly is posted with eSign's IAM token and its answer is not kept;
every other URL gets the webhook's own secret and nothing of ours.

notify's token is minted for the Hanzo API rather than for eSign itself, and a
bearer eSign's own client minted is refused.
2026-10-20 18:18:40 -07:00
..
2025-02-13 14:10:38 +11:00
2023-11-06 13:01:07 +11:00
2025-02-13 14:10:38 +11:00
2026-08-29 18:44:19 -07:00