Feature Request
Problem Statement
Inconsistent and insecure authentication across API endpoints makes it hard for integrators to adopt the API and increases security risk for paid/partner tiers.
Proposed Solution
Add a pluggable Authentication & Authorization module that supports API keys, OAuth2 client credentials, and JWT claims. Provide middleware for token verification, scope/permission checks, and admin endpoints for key lifecycle management.
Alternatives Considered
Relying on ad-hoc middleware in each service increases duplication and surface for mistakes. Third-party identity providers are useful but must be optional.
Additional Context
Grant reviewers value measurable security and onboarding signals (e.g., supported auth modes, demo flows, and examples for partners).
Implementation Ideas (Optional)
- Middleware for Express/NestJS with adapter pattern
- DB-backed API key storage, rotation and revocation endpoints
- Example integration with OAuth2 provider (Auth0/Keycloak) and JWT introspection
Would you be willing to contribute?
Feature Request
Problem Statement
Inconsistent and insecure authentication across API endpoints makes it hard for integrators to adopt the API and increases security risk for paid/partner tiers.
Proposed Solution
Add a pluggable Authentication & Authorization module that supports API keys, OAuth2 client credentials, and JWT claims. Provide middleware for token verification, scope/permission checks, and admin endpoints for key lifecycle management.
Alternatives Considered
Relying on ad-hoc middleware in each service increases duplication and surface for mistakes. Third-party identity providers are useful but must be optional.
Additional Context
Grant reviewers value measurable security and onboarding signals (e.g., supported auth modes, demo flows, and examples for partners).
Implementation Ideas (Optional)
Would you be willing to contribute?