Add RFC 0001: federated authentication

Drafts a design for OIDC-based federated authentication that lets a
managed cloud offering issue identity tokens while keeping VPC and
air-gapped on-prem deployments free of any request-time dependency on
the cloud. Introduces a server-only TokenVerifier seam with static and
OIDC implementations, validates the design against the OSS/Cloud
invariants, and records the open decisions needed before acceptance.

https://claude.ai/code/session_01N22WDYC6vv2njR5Xu96QaC
This commit is contained in:
Claude 2026-05-16 03:32:25 +00:00
parent 5c889f8e42
commit 5e03ca977c
No known key found for this signature in database
2 changed files with 265 additions and 0 deletions

View file

@ -43,6 +43,15 @@ constraints. User-facing behavior should still be documented through
| Constants and tunables | [constants.md](../user/constants.md) |
| Transaction model public contract | [transactions.md](../user/transactions.md) |
## Design Proposals (RFCs)
RFCs are proposals under review, not current truth. The authoritative
description of shipped behavior always lives in the area docs above.
| RFC | Status | Topic |
|---|---|---|
| [0001-federated-authentication.md](rfcs/0001-federated-authentication.md) | draft | OIDC auth with a cloud control plane plus VPC/on-prem deployment |
## Project Operations
| Area | Read |