Skip to content

feat: add no-auth IAM regime as a drop-in replacement for iam-svc#933

Merged
cybermaggedon merged 1 commit into
release/v2.4from
feature/no-auth-svc
May 18, 2026
Merged

feat: add no-auth IAM regime as a drop-in replacement for iam-svc#933
cybermaggedon merged 1 commit into
release/v2.4from
feature/no-auth-svc

Conversation

@cybermaggedon

Copy link
Copy Markdown
Contributor

Adds no-auth-svc, a lightweight IAM service that permits all access unconditionally — no database, no bootstrap, no signing keys. Deploy it in place of iam-svc for development, demos, and single-user setups where authentication overhead is unwanted.

The gateway no longer hard-codes a 401 on missing credentials. Instead it asks the IAM regime via a new authenticate-anonymous operation whether token-free access is allowed. This keeps the gateway regime-agnostic: iam-svc rejects anonymous auth (preserving existing security), while no-auth-svc grants it with a configurable default user and workspace.

Includes a tech spec (docs/tech-specs/no-auth-regime.md) and tests that pin the safety boundary — malformed tokens never fall through to the anonymous path, and a contract test ensures the full iam-svc always rejects authenticate-anonymous.

@github-actions

github-actions Bot commented May 18, 2026

Copy link
Copy Markdown

Contributor License Agreement ✅

All contributors have signed the CLA. Thank you!

Adds `no-auth-svc`, a lightweight IAM service that permits all access
unconditionally — no database, no bootstrap, no signing keys.  Deploy
it in place of `iam-svc` for development, demos, and single-user
setups where authentication overhead is unwanted.

The gateway no longer hard-codes a 401 on missing credentials.
Instead it asks the IAM regime via a new `authenticate-anonymous`
operation whether token-free access is allowed.  This keeps the
gateway regime-agnostic: `iam-svc` rejects anonymous auth (preserving
existing security), while `no-auth-svc` grants it with a configurable
default user and workspace.

Includes a tech spec (docs/tech-specs/no-auth-regime.md) and tests
that pin the safety boundary — malformed tokens never fall through
to the anonymous path, and a contract test ensures the full iam-svc
always rejects `authenticate-anonymous`.
@cybermaggedon cybermaggedon force-pushed the feature/no-auth-svc branch from 327a808 to f45a0bf Compare May 18, 2026 13:08
@cybermaggedon cybermaggedon merged commit da7d10e into release/v2.4 May 18, 2026
3 checks passed
@cybermaggedon cybermaggedon deleted the feature/no-auth-svc branch May 18, 2026 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant