Revoke a session as an administrator

Overview

Revoke a session as an administrator. The authentication API establishes identity and manages the roles, grants, sessions, and service credentials used for authorization.

When to use it

• Use it when an application needs to revoke a session as an administrator.
• Use it when a client needs to sign in, inspect its identity, or an administrator needs to manage access.

Quick example

Set the base URL and replace generated identifiers or credentials with values from your installation.

curl --request DELETE \
  --url "$ORDINATE_URL/v1/auth/sessions/00000000-0000-4000-8000-000000000001" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

The cURL request identifies the target resource and asks OrdinateDB to revoke a session as an administrator. The documented 204 response is session revoked.

How it works

Reference

Required capability

admin

Authorization scope

handler-resolved target

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

Code examples

These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.

const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";

const response = await fetch(`${ordinateUrl}/v1/auth/sessions/00000000-0000-4000-8000-000000000001`, {
  method: "DELETE",
  headers: {
    Authorization: `Bearer ${token}`
  }
});

if (!response.ok) {
  throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}

const data = null;
console.log(data);