Skip to Content

Refused connector signatures are logged and alert

Shipped 2026-10-27

A connector request whose signature did not match was answered 403 and written to connector_history, and nothing else. On 27 October we found that every Accordion batch containing an accented name had been refused this way since go-live, with no alert.

Each refusal now logs connector.signature_rejected (warn) with the vendor, client id, endpoint, body length and how non-ASCII characters were encoded, never the body. The [IBA] Connector signature rejected monitor posts to #iba-alerts per client.

The encoding fields tell the two usual causes apart: raw non-ASCII bytes with a failed signature mean the sender signs a different encoding than it sends; a plain-ASCII body that fails points at a wrong secret.

Last updated on