chore: collect auth-server wiki and lib refresh

Picks up the rewritten auth-server wiki (platform anatomy theme) and the
regenerated lib artifacts, including the new pep-typed marker bounce.
This commit is contained in:
2026-09-16 19:51:24 +05:30
parent 7aadae1736
commit a115df113d
12 changed files with 233 additions and 154 deletions

View File

@@ -70,7 +70,7 @@
<div data-md-component="skip">
<a href="#aetoskia-auth-server" class="md-skip">
<a href="#aetoskia-auth-server-central-identity-for-the-aetos-platform" class="md-skip">
Skip to content
</a>
@@ -386,18 +386,9 @@
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#why-centralize-authentication" class="md-nav__link">
<a href="#key-features" class="md-nav__link">
<span class="md-ellipsis">
Why centralize authentication?
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#sections" class="md-nav__link">
<span class="md-ellipsis">
Sections
🚀 Key Features
</span>
</a>
@@ -406,16 +397,25 @@
<li class="md-nav__item">
<a href="#endpoints-at-a-glance" class="md-nav__link">
<span class="md-ellipsis">
Endpoints at a glance
Endpoints at a Glance
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#service-identity" class="md-nav__link">
<a href="#documentation-structure" class="md-nav__link">
<span class="md-ellipsis">
Service identity
📁 Documentation Structure
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#related-resources" class="md-nav__link">
<span class="md-ellipsis">
🔗 Related Resources
</span>
</a>
@@ -555,52 +555,29 @@
<h1 id="aetoskia-auth-server">Aetoskia Auth Server</h1>
<h1 id="aetoskia-auth-server-central-identity-for-the-aetos-platform">🔐 Aetoskia Auth Server — Central Identity for the Aetos Platform</h1>
<p>The <strong>Aetoskia Auth Server</strong> 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.</p>
<h2 id="why-centralize-authentication">Why centralize authentication?</h2>
<blockquote>
<p><strong>Doc model:</strong> this wiki is written for humans — howto guides, examples,
and deployment recipes. The authoritative API contracts live in the code
(GSDFC docstrings) and the interactive OpenAPI reference under <code>docs/api/</code>.</p>
</blockquote>
<hr />
<h2 id="key-features">🚀 Key Features</h2>
<ul>
<li><strong>Single source of identity</strong> — one user database, one issuer, one secret.</li>
<li><strong>Uniform token contract</strong> — every service verifies the same HS256 JWT.</li>
<li><strong>No auth code duplication</strong> — services delegate with <code>jwtlib</code> or a
generated OpenAPI dependency.</li>
<li><strong>Instant revocation surface</strong>introspection gives services a live
<code>active</code> check rather than trusting expiry alone.</li>
<li>🔑 <strong>Centralized identity</strong> — one user database, one issuer, one secret</li>
<li>🎟️ <strong>Uniform token contract</strong> — every service verifies the same HS256 JWT</li>
<li>🧩 <strong>No auth code duplication</strong> — services delegate with <code>jwtlib</code> or a
generated OpenAPI dependency</li>
<li><strong>Instant revocation surface</strong><code>/introspect</code> gives services a live
<code>active</code> check rather than trusting expiry alone</li>
<li>🔓 <strong>Stateless logout</strong> — no server-side sessions; the client discards the token</li>
</ul>
<h2 id="sections">Sections</h2>
<table>
<thead>
<tr>
<th>Section</th>
<th>What you'll find</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="01_centralized_auth/">Centralized Auth</a></td>
<td>The identity model and how the ecosystem trusts the server</td>
</tr>
<tr>
<td><a href="02_how_to_use/">How to Use</a></td>
<td>Register, login, and call endpoints with tokens</td>
</tr>
<tr>
<td><a href="03_platform_integration/">Platform Integration</a></td>
<td>How services authenticate requests</td>
</tr>
<tr>
<td><a href="04_deployment/">Deployment</a></td>
<td>Environment, Docker, and CI/CD</td>
</tr>
<tr>
<td><a href="05_development/">Development</a></td>
<td>Local setup, tests, and regenerating the spec</td>
</tr>
</tbody>
</table>
<h2 id="endpoints-at-a-glance">Endpoints at a glance</h2>
<hr />
<h2 id="endpoints-at-a-glance">⚡ Endpoints at a Glance</h2>
<table>
<thead>
<tr>
@@ -642,13 +619,47 @@ service can trust one issuer instead of shipping its own auth logic.</p>
</tr>
</tbody>
</table>
<h2 id="service-identity">Service identity</h2>
<hr />
<h2 id="documentation-structure">📁 Documentation Structure</h2>
<table>
<thead>
<tr>
<th>Section</th>
<th>What you'll find</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="01_centralized_auth/">Centralized Auth</a></td>
<td>The identity model and how the ecosystem trusts the server</td>
</tr>
<tr>
<td><a href="02_how_to_use/">How to Use</a></td>
<td>Register, login, and call endpoints with tokens</td>
</tr>
<tr>
<td><a href="03_platform_integration/">Platform Integration</a></td>
<td>How services authenticate requests</td>
</tr>
<tr>
<td><a href="04_deployment/">Deployment</a></td>
<td>Environment, Docker, and CI/CD</td>
</tr>
<tr>
<td><a href="05_development/">Development</a></td>
<td>Local setup, tests, and regenerating docs</td>
</tr>
</tbody>
</table>
<hr />
<h2 id="related-resources">🔗 Related Resources</h2>
<ul>
<li><strong>Title:</strong> Aetoskia Auth Server</li>
<li><strong>Version:</strong> 0.0.5</li>
<li><strong>API spec:</strong> <code>docs/api/openapi.json</code> (rendered in the API reference site)</li>
<li><strong>Source Code:</strong> <a href="https://git.aetoskia.com/aetos/auth-server">Gitea Repository</a></li>
<li><strong>API Reference:</strong> interactive Swagger UI rendered from <code>docs/api/openapi.json</code></li>
<li><strong>CI/CD:</strong> Drone pipeline ships tagged releases as <code>aetos/auth-server</code> images</li>
</ul>
<hr />
<p>© Aetoskia Internal — <code>auth-server</code> 0.0.5</p>