swagger-api / swagger-api/swagger-ui
Addition of audience parameter to oauth config
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
The current Oauth configuration contains the following parameters:
- clientId
- clientSecret
- realm
- appName
- scopeSeparator
- additionalQueryStringParams
- useBasicAuthenticationWithAccessCodeGrant
- usePkceWithAuthorizationCodeGrant
The audience parameter is missing from this selection and would be quite useful in many authentication scenarios. Auth0, for example, can only provide a full access token if the audience parameter is received in the request body. This is the same problem raised in this stackoverflow issue, where the only apparent viable solution is to intercept the request and add the audience parameter to the body.
ps: I have already forked. Waiting a review of this to open the PR.
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
No file or test is identified. Start by tracing the OAuth configuration and token request handling in Swagger UI, then determine where an audience value belongs in the request; done means the configuration accepts it and the generated token request includes it, with Auth0 behavior covered by verification or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100