feat: add token management and Bearer auth for LLM API gateway - #195
Open
BeiBaiNian wants to merge 1 commit into
Open
feat: add token management and Bearer auth for LLM API gateway#195BeiBaiNian wants to merge 1 commit into
BeiBaiNian wants to merge 1 commit into
Conversation
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
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.
Why
The /v1/chat/completions gateway endpoint has no authentication at all: anyone who knows the address can burn upstream LLM quota through the configured channels. Following the mentor's three-tier priority (working features → user experience → security), this PR delivers the milestone 1.3 core: API token management with Bearer authentication, plus rate limiting, a model allowlist and expiration times. Secret keys are stored as plaintext per (the project is locally deployed; encryption is deferred), and that does not block this PR.
Changes
Backend:
sk--prefixed 48-char random secret key generation; masked keys in list responses; validateToken checks (non-empty name/displayName, RFC3339 expire time, at most 200 allowed models with at most 100 chars each, status enum).Frontend:
Docs:
Tests:
Verification
Automated:
End-to-end (local port 17000, a DeepSeek channel of type custom with a real upstream key):
Manual UI checklist (must be done by a human):