Fix setting token for security schemes other than basic and bearer #252
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 use-case I have for this is combination of session cookie and CSRF protection header.
While the cookie is handled automatically by browser, the token can be set manually in the Authentication section. However it can't be set using
setAuthenticationConfiguration
method, because the conditions only allow certain schemes to be configured.Rather than preventing valid cases, the method should allow configuring any security scheme, even if it doesn't necessarily make sense.