fix: auto adds api key header to swagger requests#92
Merged
Conversation
Signed-off-by: Amit Singh <singhamitch@outlook.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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
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.
Summary by cubic
Swagger UI now auto-adds the
X-API-Keyheader to all requests so protected endpoints work during in-browser testing. The OpenAPI spec definesApiKeyAuth, and tests/envs usedemo-api-key.ApiKeyAuthto OpenAPI and set it as a global security requirement.ApiKeyAuthin Swagger UI withdemo-api-key.compose.yamlto usedemo-api-key; regenerated server to setApiKeyAuthscopes in request context.Written for commit 52a93b4. Summary will update on new commits.