swagger-api / swagger-api/swagger-ui
client_credentials and authorization_code cannot be used simultaneously
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
In UseSwaggerUI calling OAuthUsePkce makes the client_secret textbox disappear for all flows. It is therefore impossible to use client_credentials (which requires a client_secret) and authorization_code (which requires this field to be absent) at the same time.
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 by tracing the UseSwaggerUI and OAuthUsePkce entry points in the JavaScript UI code and inspect how the selected OAuth flows control the client_secret field. Verify the behavior for both client_credentials and authorization_code together, ensuring each flow receives the appropriate field treatment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100