Skip to content

🔐 Aetoskia Auth Server — Central Identity for the Aetos Platform

The Aetoskia Auth Server is the central identity service of the Aetos Platform ecosystem. It issues, validates, and introspects short-lived JWT access tokens against a single shared user store backed by MongoDB, so every service can trust one issuer instead of shipping its own auth logic.

Doc model: this wiki is written for humans — how‑to guides, examples, and deployment recipes. The authoritative API contracts live in the code (GSDFC docstrings) and the interactive OpenAPI reference under docs/api/.

🚀 Key Features

  • 🔑 Centralized identity — one user database, one issuer, one secret
  • 🎟️ Uniform token contract — every service verifies the same HS256 JWT
  • 🧩 No auth code duplication — services delegate with jwtlib or a generated OpenAPI dependency
  • ⚡ Instant revocation surface — /introspect gives services a live active check rather than trusting expiry alone
  • 🔓 Stateless logout — no server-side sessions; the client discards the token

⚡ Endpoints at a Glance

Method Path Purpose
POST /register Create a user account
POST /login Authenticate and issue a JWT
GET /me Current user (Bearer)
POST /logout Stateless logout (Bearer)
POST /introspect Service-to-service token verification
GET /health Health check

📁 Documentation Structure

Section What you'll find
Centralized Auth The identity model and how the ecosystem trusts the server
How to Use Register, login, and call endpoints with tokens
Platform Integration How services authenticate requests
Deployment Environment, Docker, and CI/CD
Development Local setup, tests, and regenerating docs
  • Source Code: Gitea Repository
  • API Reference: interactive Swagger UI rendered from docs/api/openapi.json
  • CI/CD: Drone pipeline ships tagged releases as aetos/auth-server images

© Aetoskia Internal — auth-server 0.0.5