OAuth Scopes - DO NOT MERGE #1
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
… this scope. In the OpenAPI v3 specification, Security Scheme Object requires a map of scopes, but doesn't specify "non-empty." The Security Requirement Object strongly implies that a non-empty array of scopes is required, but again doesn't specify. KaiZen OpenAPI Editor treats the empty scopes array as invalid. I'll take this up with the OpenAPI specification working group. If empty scopes is allowed in security scheme, it must be allowed in requirements. Conversely, if it's optional in security requirement object, it must be optional in the security scheme.\ In the meantime, I've added this "unspecified" scope and referenced that from security requirements. This gets around the issue for now.
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.
Inspecting changes.