Skip to content

Break-Glass Session Cannot Acknowledge

URI: https://docs.ankatech.co/errors/break-glass-session-cannot-acknowledge
HTTP Status: 403 Forbidden

When you see this

A security alert was acknowledged from a break-glass session — a session opened through the emergency-access entry, whose access token carries break_glass: true. The session that raised an alert never clears it, so the request was refused, nothing changed, and the refusal was recorded in the audit trail.

Common Causes

  • You are still signed in through emergency access and opened the security alerts screen to acknowledge the alert your own sign-in raised.

Response Example

{
  "type": "https://docs.ankatech.co/errors/break-glass-session-cannot-acknowledge",
  "title": "Break-Glass Session Cannot Acknowledge",
  "status": 403,
  "detail": "A break-glass session cannot acknowledge a security alert. Sign in normally to acknowledge it. Nothing was changed.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/security-alerts/5c9e2f14-8b3a-4d71-9e6c-2a1f7d0b4e83/acknowledgment",
  "timestamp": 1760951700,
  "extensions": {
    "requestId": "4e2a9c71-0b3d-4f58-a6e1-9d7c2b5f8e30"
  }
}

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. Sign out of the break-glass session.
  2. Sign in normally as an administrator who holds the permission to acknowledge security alerts — the same person signed in as their normal account is admitted.
  3. Acknowledge the alert, with a note describing why break-glass access was used.

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