OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
POST/v1/auth/login/local

Sign in with local credentials

operation ID: post_v1_auth_login_local

Overview

Sign in with local credentials. 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 sign in with local credentials.
  • 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 POST \
  --url "$ORDINATE_URL/v1/auth/login/local" \
  --header "Content-Type: application/json" \
  --data '{
    "username": "string",
    "password": "string"
  }'

Expected output · 204

Session created; response sets the HttpOnly session cookie

No response body.

The cURL request sends the smallest contract-derived body and asks OrdinateDB to sign in with local credentials. The documented 204 response is session created; response sets the HttpOnly session cookie.

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
anonymous
Authorization scope
none

Parameters

No parameters.

Request body

application/json

passwordstringrequired
format: password · write only
usernamestringrequired
unknown fields rejected

Example request body

{
  "username": "string",
  "password": "string"
}

Responses

204Session created; response sets the HttpOnly session cookie

No response body.

401Invalid credentials

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"
}
403Account is sealed

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/login/local`, {
  method: "POST",
  headers: {
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
  "username": "string",
  "password": "string"
})
});

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

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