CSR_NOT_ACCEPTED

Certificate signing request not accepted: what the CSR_NOT_ACCEPTED error means and how to fix it.

HTTP 422. Problem type: https://docs.ovok.com/errors/csr-not-accepted.

What this means

Ovok could not issue a client certificate from the certificate signing request (CSR) you sent. The message says why: the body holds no PEM CSR, its signature does not verify, its key is neither an EC key on P-256 or P-384 nor an RSA key of at least 2048 bits, or its EC key spells out its curve instead of naming it. Nothing was issued or registered.

Troubleshooting

  1. Make the CSR with the key your client will present, and send it PEM-encoded in csr. Never send the private key.
  2. Use an EC key on P-256 or P-384 that names its curve, or an RSA key of at least 2048 bits: openssl req -new -newkey ec -pkeyopt ec_paramgen_curve:prime256v1 -pkeyopt ec_param_enc:named_curve -nodes -keyout client.key -out client.csr -subj "/CN=client". Without ec_param_enc:named_curve, the openssl that ships with macOS (LibreSSL) spells the curve out; OpenSSL 3 names it either way.
  3. Check the CSR with openssl req -in client.csr -noout -verify.

Retry safely

Retry with a corrected CSR. An unchanged request returns the same error.

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