Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to inject JAX-RS ResourceInfo into custom HTTP Security Policy #39917

Conversation

michalvavrik
Copy link
Member

fixes: #38940

@michalvavrik
Copy link
Member Author

michalvavrik commented Apr 5, 2024

cc @JChrist I've added test that basically does what you need, so that it's tested (well, for blocking you have the blocking executor, that doesn't need to be tested, we use it extensively)

Copy link

quarkus-bot bot commented Apr 5, 2024

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit b8f40df.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

⚠️ There are other workflow runs running, you probably need to wait for their status before merging.

@michalvavrik michalvavrik force-pushed the feature/allow-to-inject-resourceinfo-into-http-security-policy branch from b8f40df to d044f82 Compare April 5, 2024 17:08
Copy link

quarkus-bot bot commented Apr 5, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit d044f82.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@quarkus-bot quarkus-bot bot added the triage/invalid This doesn't seem right label Apr 5, 2024
@michalvavrik michalvavrik deleted the feature/allow-to-inject-resourceinfo-into-http-security-policy branch April 5, 2024 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging this pull request may close these issues.

Offer a way to block inside custom SecurityContext.isUserInRole with resteasy-reactive
2 participants