feat: Set bearerAuth global when SecurityScheme is empty #301
Conversation
This file contains 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
manuraf
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
List of Changes
This pull request introduces a modification to handle an issue when merging with OpenAPI specifications generated via Quarkus happens. Specifically, the generated OpenAPI includes an empty security schema, which needs to be replaced with a bearerAuth global.
Motivation and Context
This update addresses an issue where the OpenAPI specification generated by Quarkus includes an empty SecurityScheme, which is not valid for API security. By replacing this with a bearerAuth scheme, the OpenAPI spec will correctly define security requirements for the endpoints.
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: