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

no security at operation level #19

Open
bymaximus opened this issue Oct 17, 2017 · 2 comments
Open

no security at operation level #19

bymaximus opened this issue Oct 17, 2017 · 2 comments

Comments

@bymaximus
Copy link

theres no security related data at paths operations?

@MikeRalphson
Copy link
Contributor

MikeRalphson commented Oct 17, 2017

Correct, there is no security at PathItem level. At Operation level yes, this is still on the specification support TODO list.

If you're asking about the old (red and blue) v2 version for Swagger/OpenAPI 2.0 only, then this is also a TODO item, but this branch is no-longer maintained, unless someone volunteers to take it on.

First is to add a series of check-boxes for each defined securityScheme, then add relevant scopes for oAuth2 security. I can try and get this done during the week, or PRs are gratefully accepted.

@MikeRalphson MikeRalphson self-assigned this Oct 17, 2017
@MikeRalphson MikeRalphson changed the title no security at path no security at operation level Oct 17, 2017
@MikeRalphson
Copy link
Contributor

Hi @bymaximus the ability to set the security at operation level to default, none or custom and to select the set of custom securitySchemes is done. Not yet done is editing scopes for oauth2 schemes.

If you toggle the custom security checkbox it will bring in all the defined security schemes and you can delete the ones you don't want.

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

No branches or pull requests

2 participants