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.
I managed to implement an OpenApi security schemes as shown here so JWT authorization will be shown in a specific chapter and not amongst other headers.
I'm not sure if I did it right though as it needs a name for each authorization to be assigned. I decided to use constant name
"JWT authorizer"
as there is no difference in a presentation of the API between separate jwt authorizations after all even if one decides to use many authorization layers. As an option, it is possible to usetype_name::<T>
ofT
fromJwtClaims<T>
but this will lead to an inner structure leakage to the API. Maybe there are other ways but I can't come up with one.