Authentication - blame (4c6d2a) – AeThex

Blame

572610	Anonymous	2026-06-20 21:50:43
Add AeThex documentation page

# Authentication

4c6d2a	Anonymous	2026-06-23 03:31:07

Authentication explains how users, services, and integrations prove identity before accessing AeThex systems.

572610	Anonymous	2026-06-20 21:50:43
Add AeThex documentation page

4c6d2a	Anonymous	2026-06-23 03:31:07

<h2>Authentication model</h2>

  <p>Authentication starts with Passport and extends into API, app, and organization access.</p>

</div>

572610	Anonymous	2026-06-20 21:50:43
Add AeThex documentation page

4c6d2a	Anonymous	2026-06-23 03:31:07

AeThex authentication should be handled through [[Passport]] wherever possible. Passport acts as the user-facing identity layer, while APIs and backend services validate sessions, tokens, or service credentials against that identity context.

## Common flows

- User sign-in through [[Passport]].

- Account linking through [[Linked-Accounts]].

- Organization access checks through [[Organizations]] and [[Teams]].

- API requests authenticated through documented credentials in [[Api-Reference]].

- Automation and local tooling authenticated through [[CLI]] or [[SDKs]].

## Implementation checklist

1. Choose the identity flow: user session, linked account, or service credential.

2. Request only the scopes needed for the integration.

3. Validate tokens server-side before trusting user claims.

4. Check [[Permissions]] after authentication; identity alone is not authorization.

5. Log security-relevant failures for audit and support.

<a class="docs-card" href="/Passport">Passport</a>

<a class="docs-card" href="/Permissions">Permissions</a>

<a class="docs-card" href="/Security">Security</a>

<a class="docs-card" href="/Api-Reference">API Reference</a>

</div>

> [!WARNING]

> Do not store long-lived secrets in client-side code, public repos, browser storage, or Discord bot commands.