Support for Proxy-Authorization in http security scheme
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 3
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 1
Description
Hi - the OpenAPI 3.0.3 specification implies here that for the http security scheme only Authorization header from RFC7235 may be used to supply credentials, such as a bearer token. Would it be at all possible to include support for Proxy-Authorization (without the need to use a specification extension)? The use case is to supply separate proxy and target credentials in one API request.
Contributor guide
No contributing guide indexed for this repository
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 reading the OpenAPI 3.0.3 Security Scheme Object section linked in the issue, then locate where this repository handles HTTP security schemes. Confirm how Proxy-Authorization could coexist with Authorization and define the expected behavior for supplying separate proxy and target credentials without a specification extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100