# CERTIFICATE_NOT_ACCEPTED

Canonical page: https://docs.ovok.com/errors/certificate-not-accepted

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/certificate-not-accepted`](https://docs.ovok.com/errors/certificate-not-accepted).

## What this means [#what-this-means]

Ovok could not register the certificate you sent as one of the project's client certificates. The message says why: the body holds no PEM certificate, it is a CA certificate, it is not valid now, it is not for client authentication, or no CA Ovok trusts issued it. Nothing was registered.

## Troubleshooting [#troubleshooting]

1. Send the certificate itself, PEM-encoded, in `certificate`. Never send its private key.
2. Check its dates and usage with `openssl x509 -in client.crt -noout -dates -ext extendedKeyUsage`. A client certificate needs `TLS Web Client Authentication`, or no extended key usage at all.
3. Get the certificate issued by the CA your Ovok environment trusts. Ask Ovok which one that is.

## Retry safely [#retry-safely]

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

## If the problem persists [#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](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
