Skip to content

Conversation

@aditya-damerla128
Copy link
Collaborator

@aditya-damerla128 aditya-damerla128 commented Jan 8, 2026

Link to the Demo

Summary

Implements scoped API key authentication system per #37.

What's done:

  • SQLite database with users, api_keys, sessions tables
  • Two key types: ozw_ (general) and ozw_scoped_ (limited)
  • Dashboard auth + API key management endpoints
  • Real API key validation on /v1/chat/completions
  • Server-side LLM provider config (no more "ollama" API key hack)
  • Live Demo section for testing the flow

Still TODO:

  • Production-ready PostgreSQL migration
  • Rate limiting per key
  • Usage tracking/analytics
  • Key rotation support

Closes #37

Add complete API key authentication infrastructure:
- SQLite database with users, api_keys, and sessions tables
- Two key types: ozw_ (general) and ozw_scoped_ (limited)
- Dashboard auth routes (/auth/register, /auth/login)
- API key management routes (/v1/api-keys)
- Real API key validation middleware for /v1/chat/completions
- Server-side LLM provider config (removes "ollama" API key hack)
- Live Demo section with API test dialog

Closes #37
@aditya-damerla128
Copy link
Collaborator Author

Will be checking the failing workflows after the methodolgy is settled on if this is the way we want to go forward with the implementation

@aditya-damerla128
Copy link
Collaborator Author

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.

Scoped API Keys

2 participants