feat: bearer authorization on swagger ui #107
Open
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
TeeWallz
changed the title
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.
Description
While bearer authorization has been implemented, there is no way to utilize this via the Swagger UI in current state.
This MR introduces this value via teh standard jwt mechanism. It also corrects the jwt token prefix to the use standard 'bearer' prefix to align with the jwt standard. Without this change, the bearer token generated fails the 'token' string check.
PR Checklist (Please do not remove)
type(scope): descriptionortype: descriptionformatAdd a failing test that passes with the changes introduced in this PR, or explain why it's not feasibleAdd documentation for the feature or changes introduced in this PR to the docs; you can run them withbun docs