[UI] Add support for apiKey in query and cookie param #1151
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
This PR consists of added support for allowing Security Schemes with the type of
apiKey
to be used for the following parameter types:in: query
in: cookie
Although the original issue proposes that the value should be shown in the UI, we will continue to mask credentials to align with best security practices - while still allowing the user to make the underlying request within the Request Demo Panel.
Motivation and Context
See #1150 for context.
How Has This Been Tested?
Tested with the following spec and ensured that request can be made from Request Demo Panel:
Screenshots (if appropriate)
Tested request from Demo Panel
Updated Authentication Table to reflect
in
parameter (previously hard coded to 'Header')Types of changes
Checklist