Skip to content

Federation Domain Verification Required

URI: https://docs.ankatech.co/errors/federation-domain-verification-required
HTTP Status: 409 Conflict

When you see this

Enabling an identity provider was refused because the applicable verified email-domain set is empty. With no verified domain declared, the verified-domain gate on the login path would refuse every federated identity that asserts a domain, so the provider could admit nobody and enabling it would produce a configuration that cannot work.

Common Causes

  • No email domain has ever been declared as verified for this deployment.
  • Every declared domain was removed or is not applicable to the tenant the provider is being enabled for.

Response Example

{
  "type": "https://docs.ankatech.co/errors/federation-domain-verification-required",
  "title": "Federation Domain Verification Required",
  "status": 409,
  "detail": "This deployment has no verified email domain, so federated logins could not be admitted. Declare at least one email domain before enabling the identity provider.",
  "instance": "/api/v3/admin/platform/idp/3f2504e0-4f89-11d3-9a0c-0305e82c3301/enable",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000",
    "prerequisite": "VERIFIED_DOMAIN_REQUIRED"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. extensions.prerequisite is the machine-readable form of the missing precondition.

The status is 409 rather than 403 or 422 on purpose: the caller is authorized, there is no request body to be unprocessable, and the provider exists. What is missing is a precondition on the deployment's own state, so neither "you lack permission" nor "your request was malformed" would send the operator to the right place.

How to Resolve

  1. Declare at least one verified email domain for the deployment.
  2. Confirm the domain is applicable to the tenant whose provider you are enabling.
  3. Re-issue the enable request.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.