Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openapi3 fails to parse empty securityRequirement #18

Open
mdellweg opened this issue Aug 26, 2020 · 0 comments
Open

openapi3 fails to parse empty securityRequirement #18

mdellweg opened this issue Aug 26, 2020 · 0 comments

Comments

@mdellweg
Copy link

The comment in https://github.com/Dorthu/openapi3/blob/master/openapi3/paths.py#L304 claims that a securityRequirement must be a dictionary with exactly one key.
But https://swagger.io/specification/#securityRequirementObject specifies that "Security Requirement Objects that contain multiple schemes require that all schemes MUST be satisfied for a request to be authorized.". And it provides an Example with an empty securityRequirement ({}).
This example would fail to pass in openapi3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant