OpenAPITools / OpenAPITools/openapi-generator
[BUG][ASPNETCORE] Fallback to HttpContext as resource in authorization handler
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
Referencing this announcement and this more helpful StackOverflow Answer, we need to make a change in the ApiAuthentication file with the AuthorizationHandler to fallback to HttpContext because that is the new default resource that will be provided to the handler.
openapi-generator version
7.18
I'll open a PR shortly with my suggested changes, which is just supporting both.
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 locating the ASPNETCORE ApiAuthentication file and its AuthorizationHandler implementation; compare the current resource handling with the linked announcement and StackOverflow answer. Done means the handler supports both the existing resource and HttpContext, with relevant ASPNETCORE generation or tests confirming the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100