Error code provider_discovery_failed (HTTP 422)
What Synq's `provider_discovery_failed` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
An OpenID Connect issuer's discovery document couldn't be read at <issuer>/.well-known/openid-configuration, isn't one, or names another issuer than the one sent.
What to do
Check the issuer with its administrator: send exactly the issuer its discovery document names.
| Field | Value |
|---|---|
code | provider_discovery_failed |
status | 422 Unprocessable Content |
title | Provider discovery failed |
Synq's APIs answer errors with a problem document (RFC 9457, application/problem+json). Its type is the address of this page, and its code is provider_discovery_failed. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/provider_discovery_failed",
"title": "Provider discovery failed",
"status": 422,
"code": "provider_discovery_failed"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code provider_url_unsafe (HTTP 422)
What Synq's `provider_url_unsafe` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
Error code sign_in_provider_exists (HTTP 409)
What Synq's `sign_in_provider_exists` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.