swagger-api / swagger-api/swagger-ui
OAS3 OAuth2 Multiple-Flow Security Schemes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
| Q | A |
|---|---|
| Bug or feature request? | Bug |
| Which Swagger/OpenAPI version? | 3.0 |
| Which Swagger-UI version? | 3.x |
| How did you install Swagger-UI? | ... |
| Which browser & version? | Chrome 61 |
| Which operating system? | High Sierra |
Demonstration API definition
Gist: https://gist.github.com/shockey/7587cca232341ea95766d22eb67ba11f
Configuration (browser query string, constructor, config.yaml)
Default.
Expected Behavior
Each flow in a multiple-flow security scheme should be treated independently.
Current Behavior
Flows in the same scheme get the same authorization state indication and error messages.
Possible Solution
Rewire the IDs being used to track the available security schemes to use unique keys for flows within the same scheme.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the demonstration API definition in the linked Gist and reproduce it in Swagger UI 3.x using the default configuration. Trace how authorization state and error messages are tracked for the multiple flows, then verify that each flow is handled independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100