SIGNALS_MTLS_REQUIRED

Client certificate required: what the SIGNALS_MTLS_REQUIRED error means and how to fix it.

HTTP 403. Problem type: https://docs.ovok.com/errors/signals-mtls-required.

What this means

The project has SIGNALS_MTLS_ENABLED on, so every call into Signals through Ovok must present one of its registered client certificates in the TLS handshake. This call presented none. Nothing was sent to Signals.

Troubleshooting

  1. Configure your HTTP client with the client certificate and its private key. In Node, pass cert and key to the agent; with curl, use --cert and --key.
  2. Check that the call goes to the API host directly. A proxy that ends TLS in front of your client drops the certificate.
  3. Ask a project admin whether mTLS should be on. Turning SIGNALS_MTLS_ENABLED off lets calls without a certificate through again.

Retry safely

Retry once the client presents its certificate. The refused call changed nothing.

If the problem persists

Share the HTTP status, problem type, request path, response timestamp and traceId with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The Error responses guide explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page