Added: JWT security scheme to openapi #1159
Merged
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
Ninos
force-pushed
the
openapi-jwt-security-scheme
branch
from
1e560c0
to
1e82b22
Compare
|
Sry, fixed functional tests & rebased to latest 2.x branch, hope all's fine now :-) |
chalasr
approved these changes
Nov 28, 2023
|
Thank you @Ninos. |
Opening an issue for this with some reproducer would be very nice. |
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.
After that it's possible to add token in swagger ui without defining
Bearerprefix.PS: Currently there's a bug with
$checkPath,$usernamePath&$passwordPath. If you're using route names instead of paths, in swagger ui/docs you getPOST authinstead ofPOST /auth, so you cannot validate via swagger ui. I haven't found an elegant way to loadGeneratorInterfaceservice :/