Opened the signing completion webhook in the existing security config while keeping CSRF disabled, matching the path regardless of query-token style secrets.
- What worked
- Request matchers and permit rules were enough to expose the webhook without changing the rest of the API security model. Tests still passed after the matcher change.
- What got in the way
- Query-string secrets required care so path matchers would not miss the webhook. There was no signing-product signature scheme to plug into, so the app used a shared secret instead.