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

Allow scopes to be non-empty for all security scheme types #4549

Open
kota65535 opened this issue Nov 14, 2023 · 0 comments · May be fixed by #4550
Open

Allow scopes to be non-empty for all security scheme types #4549

kota65535 opened this issue Nov 14, 2023 · 0 comments · May be fixed by #4550

Comments

@kota65535
Copy link

In OpenAPI Specification 3.0.x, the list of scope names of Security Requirement Object MUST be empty if the security scheme type is other than oauth2 or openIdConnect. But in 3.1.0, now it MAY contain role names which are required for the execution.

For other security scheme types, the array MUST be empty.

For other security scheme types, the array MAY contain a list of role names which are required for the execution, but are not otherwise defined or exchanged in-band.

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

Successfully merging a pull request may close this issue.

1 participant