#9843: Sort out OAuth scopes for individual endpoints#12410
Open
ionel-sirbu-crunch wants to merge 3 commits intoswagger-api:3.0.0from
Open
#9843: Sort out OAuth scopes for individual endpoints#12410ionel-sirbu-crunch wants to merge 3 commits intoswagger-api:3.0.0from
ionel-sirbu-crunch wants to merge 3 commits intoswagger-api:3.0.0from
Conversation
…ndpoint as a subset of the scopes defined in the `securitySchemes`.
Author
|
Is there anything I need to do here? I don't quite understand from the auto-generated comment about workflows... |
frantuma
force-pushed
the
3.0.0
branch
6 times, most recently
from
c824674 to
7e5274a
Compare
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.
This is a fix for issue #9843 .
According to the OpenAPI spec, one is supposed to define the superset of all OAuth scopes available globally for an API under the
securitySchemesblock, then reference only a required subset from those scopes for an individual endpoint. Example here.As described in issue #9843 , the generated data model that is passed to the templating engine, regardless of language chosen, always uses the full list of OAuth scopes defined globally, ignoring the subset of references used for individual endpoints.
For context, I'm using
io.swagger.codegen.v3:swagger-codegen-maven-pluginfor my requirements, converting to static html (API documentation).