Enable apikey security for all methods. #194
Open
Conversation
This file contains hidden or 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
Also explicitly specify apikey auth for methods that require oauth2, since otherwise the local setting (oauth2 only) would override the global setting (apikey only). The result is that these methods require both oauth2 and apikey authentication. Without this fix, go-swagger doesn't generate an API that allows an authentication method to be specified.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Also explicitly specify apikey auth for methods that require oauth2,
since otherwise the local setting (oauth2 only) would override the
global setting (apikey only). The result is that these methods
require both oauth2 and apikey authentication.
Without this fix, go-swagger doesn't generate an API that allows an
authentication method to be specified.
Fixes #193