alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: track all project map and index files

Browse Source 
Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).
This commit is contained in:
Developer
2026-06-12 13:46:23 +00:00
parent 44ef62271e
commit 070cd4d5a5
642 changed files with 14785 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/2026-05-17-auth-oauth/.pi-map.md
+23
View File
@@ -0,0 +1,23 @@
# openspec/changes/archive/2026-05-17-auth-oauth
dir: openspec/changes/archive/2026-05-17-auth-oauth
index: openspec/changes/archive/2026-05-17-auth-oauth/.pi-map.index.md
## role
Archive of a 2026-05-17 design proposal for implementing OAuth2/OIDC authentication with Authentik integration in a backend API.
## files
- .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
- README.md | Documents a project that implements OAuth2/OIDC authentication using Authentik with internal JWTs and database-backed refresh tokens | dep: Authentik, OAuth2, OIDC, JWT
- design.md | Design document specifying an OAuth2/OIDC authentication system using Authentik with internal JWT access tokens, DB-backed opaque refresh tokens, and environment-aware cookie policies. | dep: Authentik, Python async SQLAlchemy, Alembic, JWT library, JWKS client, cookie handling library
- proposal.md | Proposes a technical implementation plan for adding production-ready OAuth2/OIDC authentication with Authentik integration, JWT session management, and secure token lifecycle handling to a backend API project. | dep: Authentik, OAuth2/OIDC, JWKS, JWT, database, apps/api/src, config, models, auth services, API routes
- tasks.md | Task tracking document for implementing OIDC/JWT authentication system with refresh tokens in a backend application. | dep: SQLAlchemy, Alembic, Authentik OIDC, pytest, ruff, mypy, asyncpg, PostgreSQL
## arch
Specification-driven design documentation using OpenAPI metadata, with phased implementation planning (proposal → design → tasks → README) for a hybrid token architecture (JWT access tokens + opaque DB-backed refresh tokens) with environment-aware security policies.
## tags
oidc, authentik, oauth2, jwt, authentication, tokens, refresh, design
## symbols
-
## workflows
-
## dirty
-