PROVISION_SECRET_REFUSED
Provisioning secret refused: what the PROVISION_SECRET_REFUSED error means and how to fix it.
HTTP 401. Problem type: https://docs.ovok.com/errors/provision-secret-refused.
What this means
A customer environment refused a call from the billing hub because the provisioning secret was missing or wrong. The response carries WWW-Authenticate. No customer was created or changed.
Troubleshooting
- Check that the call sends the shared secret in the
X-Ovok-Provision-Secretheader. A call without the header is refused. - Check that the hub and this environment hold the same secret. After a rotation on one side, update the other and redeploy it.
- Remove spaces and line breaks from the value you send.
- Check that the call targets the intended environment, and that it was redeployed after its secret changed.
Retry safely
Do not retry with the same secret. Retry after the secrets match. The hub pushes again on the next change to the customer's account and when it next starts. Keep the secret out of logs and tickets.
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