Skip to content

Account Not Active

URI: https://docs.ankatech.co/errors/federated-link-target-not-active
HTTP Status: 422 Unprocessable Entity

When you see this

The account you named is not active, so it cannot be bound to a federated identity.

The refusal is raised on the declare leg of federated account linking, POST /api/v3/admin/tenants/{tenantId}/users/{userId}/federated-link-intent. Nothing was written: no intent exists, no notification was sent, and the target account is unchanged.

The same condition is checked again when the link is consumed, not only when it is declared. The two checks are not duplicates: an account can be suspended inside the authorization window, and without the second check a federated sign-in would resurrect an account an administrator had just disabled.

Common Causes

  • The account is suspended, disabled, or otherwise not in an active state.
  • The account was created but its activation has not been completed.

Response Example

{
  "type": "https://docs.ankatech.co/errors/federated-link-target-not-active",
  "title": "Account Not Active",
  "status": 422,
  "detail": "This account is not active, so it cannot be bound to a federated identity.",
  "instance": "/api/v3/admin/tenants/2f1c9d84-6b2e-4d3a-9f57-0a1b2c3d4e5f/users/8c4f1a02-77d5-4e19-b3ac-51e6d9f0a742/federated-link-intent",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. This is an Admin API body, so the correlation identifier is extensions.requestId; see Error Index & Overview.

How to Resolve

  1. Read the account's current status in the console.
  2. Return the account to an active state — complete its activation, or lift the suspension — if that is the intended outcome.
  3. Declare the link intent again once the account is active.

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