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.

Sign up for GitHub

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

Jump to bottom

security not parsing "none" #492

Closed
Daxten opened this issue Jul 25, 2017 · 2 comments
Closed

security not parsing "none" #492

Daxten opened this issue Jul 25, 2017 · 2 comments
Assignees
@gracekarina
Labels
bug

Comments

@Daxten
Copy link

Daxten commented Jul 25, 2017 •
edited
Loading

see OAI/OpenAPI-Specification#14 (comment)

empty security object is not getting parsed

"security": [
  {},
  {"oauth": […]},
  {"token-1": []},
  {"token-2": []}
]

parsed has only 3 elements
@gracekarina gracekarina self-assigned this Dec 31, 2017
@gracekarina gracekarina added the bug label Jan 5, 2018
gracekarina added a commit that referenced this issue Jan 5, 2018
@gracekarina
fixing parsing of empty securityRequirement - refs #492
ad9d80c
@gracekarina gracekarina mentioned this issue Jan 5, 2018
Merged
gracekarina added a commit that referenced this issue Jan 6, 2018
@gracekarina
Merge pull request #615 from swagger-api/bug/empty-security#492
c1c5af8 
fixing parsing of empty securityRequirement - refs #492
@gracekarina
Copy link
Contributor

Hi @Daxten, Thanks for the report, please checkout if this fixes the issue in branch 2.0

@gracekarina
Copy link
Contributor

Hi, @Daxten please let us know if it's still an issue

@wsalembi wsalembi mentioned this issue Jan 22, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gracekarina gracekarina

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Daxten @gracekarina