Skip to content

[BUG][ASPNETCORE] Fallback to HttpContext as resource in authorization handler#22617

Closed
alec-petersen wants to merge 2 commits intoOpenAPITools:masterfrom
alec-petersen:fallback-to-http-context
Closed

[BUG][ASPNETCORE] Fallback to HttpContext as resource in authorization handler#22617
alec-petersen wants to merge 2 commits intoOpenAPITools:masterfrom
alec-petersen:fallback-to-http-context

Conversation

@alec-petersen
Copy link
Copy Markdown
Contributor

@alec-petersen alec-petersen commented Jan 4, 2026

Fixed #22616

Expands on existing functionality by also attempting with HttpContext.

 var httpContext = (context.Resource as AuthorizationFilterContext)?.HttpContext
    ?? context.Resource as HttpContext;

if (httpContext == null)
    return;

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 17 files

@alec-petersen
Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG][ASPNETCORE] Fallback to HttpContext as resource in authorization handler

1 participant