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

SecurityContext override with no quarkus-security #17685

Merged
merged 1 commit into from
Jun 8, 2021

Conversation

stuartwdouglas
Copy link
Member

Fixes #17527

@sberyozkin
Copy link
Member

LGTM, can you please modify some of the existing reactive resteasy test endpoints to confirm the customized SecurityContext can be injected ?

@stuartwdouglas
Copy link
Member Author

The idea is not that is can be injected, but rather that the request does not fail if quarkus-security is not present. This would need a whole new test module which is not worth it imho, as there is already a dependency on quarkus-security for the tests.

@sberyozkin
Copy link
Member

@stuartwdouglas I see, I thought overriding SecurityContext does not work at all with RwstEasy reactive...

@sberyozkin sberyozkin self-requested a review June 8, 2021 11:36
@sberyozkin sberyozkin merged commit 07bcdda into quarkusio:main Jun 8, 2021
@quarkus-bot quarkus-bot bot added this to the 2.1 - main milestone Jun 8, 2021
@gsmet gsmet modified the milestones: 2.1 - main, 2.0.0.Final Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Overriding SecurityContext doesn't work with quarkus-resteasy-reactive, but works with quarkus-resteasy
3 participants