OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/auth/roles

List authorization roles

operation ID: get_v1_auth_roles

Overview

List authorization roles. 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 list authorization roles.
  • 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

curl --request GET \
  --url "$ORDINATE_URL/v1/auth/roles" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

Expected output · 200

Roles

Example 200 output

{
  "entries": [
    {
      "role_id": "00000000-0000-4000-8000-000000000001",
      "name": "string",
      "capabilities": [
        "read"
      ],
      "system": false,
      "valid_from_ns": 0,
      "valid_to_ns": 0,
      "tx_id": 0
    }
  ]
}

The cURL request supplies the documented path and query values and asks OrdinateDB to list authorization roles. The documented 200 response is roles.

How it works

OrdinateDB resolves a session or bearer credential to a principal, then evaluates roles, capabilities, and resource scope for each protected operation.

Reference

Required capability
admin
Authorization scope
handler-resolved target

Parameters

NameInRequiredType and constraints
as_of_nsqueryno
integer

UTC Unix timestamp in nanoseconds

format: int64

Request body

This operation has no request body.

Responses

200Roles

application/json

entriesarrayrequired

array

capabilitiesarrayrequired

array

Capability
string

values: read · annotate · enter · approve · amend · model-edit · registry-manage · calc-author · display-author · display-publish · episode-manage · redact · admin

namestringrequired
role_idstringrequired
format: uuid
systembooleanrequired
tx_idintegerrequired
format: int64
valid_from_nsintegerrequired

UTC Unix timestamp in nanoseconds

format: int64
valid_to_nsany ofrequired

any of

option 1

integer

UTC Unix timestamp in nanoseconds

format: int64

option 2

null
unknown fields rejected
unknown fields rejected

Example 200 output

{
  "entries": [
    {
      "role_id": "00000000-0000-4000-8000-000000000001",
      "name": "string",
      "capabilities": [
        "read"
      ],
      "system": false,
      "valid_from_ns": 0,
      "valid_to_ns": 0,
      "tx_id": 0
    }
  ]
}
401Authentication required

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 401 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
403Required capability is not granted

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 403 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
503Model database is not configured

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 503 output

{
  "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.

JavaScript

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

const response = await fetch(`${ordinateUrl}/v1/auth/roles`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`
  }
});

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

const data = await response.json();
console.log(data);