Open
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
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.
The API authentication middleware is updated so it can recognize OAuth access tokens sent in the Authorization: Bearer header. Before this, the API only accepted fixed/static tokens. when a request comes in, the middleware now checks:
Is this a valid OAuth token?
Is it not expired?
Does it belong to a registered OAuth client and user?
If the token is valid, the request is allowed and the user is treated as authenticated. OAuth tokens work alongside existing authentication. This means: Old static tokens still work New OAuth-based clients (like ChatGPT) also work No breaking changes for existing users
Finally, the OAuth service is initialized when the server starts, so token validation is available everywhere the middleware runs.