add support for API keys including generation and revokation #1175
Conversation
This file contains 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
acoffman
added
the
new-feature
|
Tests failed because they need an environment variable set in the GitHub action config. That change is pushed to main. |
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.
This adds support for token based authentication (API Keys). In addition to the existing session based auth, users can now pass a bearer token in the http authorization header. (
Authorization: Bearer <my api key>)It adds mutations and UI for securely generating and revoking keys to your user profile page:
Screen.Recording.2024-12-23.at.12.12.29.PM.mov
There are also tests demonstrating how the functionality works.