Refactor authentication to API key-based system and optimize architecture#12
Merged
Conversation
…ate limiting. Purged legacy JWT logic, re-scoped Redis namespaces, and optimized service layer orchestration for headless architecture.
… support API key-based scoping
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sanjeevafk
added a commit
that referenced
this pull request
May 24, 2026
…ture (#12) * refactor(auth): migrate to API key-based authentication and unified rate limiting. Purged legacy JWT logic, re-scoped Redis namespaces, and optimized service layer orchestration for headless architecture. * feat: purge legacy consumer artifacts and refactor database schema to support API key-based scoping
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request makes significant changes to the authentication system and general configuration of the DepthAPI backend, focusing on removing legacy authentication logic, simplifying the codebase, and updating branding and security settings. The most important changes are summarized below:
Authentication and Security Refactoring:
api/auth.py, leaving only Supabase client initialization. This substantially simplifies authentication and offloads responsibility to external systems or other parts of the codebase. [1] [2]supabase_jwt_secret,supabase_auth_webhook_secret) fromapi/config.py, reducing potential security risks.Branding and Configuration Updates:
api/main.py, including API title, description, version, and allowed CORS origins. [1] [2] [3]Security Header Adjustments:
api/main.py, removing unused or redundant directives and references to old domains.Cleanup and Removal of Unused Files:
Dockerfile.frontend,Dockerfile.frontend.test) [1] [2]These changes collectively modernize and streamline the backend, improve maintainability, and align the project with the new DepthAPI branding.