Document RBAC used on CDI beans and IO thread when method returns "something" in a synchronous manner #29229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sberyozkin
reviewed
Nov 13, 2022
michalvavrik
force-pushed
the
feature/document-rbac-bean-method-behavior
branch
2 times, most recently
from
f61df19 to
f4e6cdc
Compare
sberyozkin
reviewed
Nov 14, 2022
michalvavrik
force-pushed
the
feature/document-rbac-bean-method-behavior
branch
from
f4e6cdc to
696cb4a
Compare
michalvavrik
force-pushed
the
feature/document-rbac-bean-method-behavior
branch
from
696cb4a to
ea47a55
Compare
sberyozkin
approved these changes
Nov 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes: #23547 (together with #26529)
Document known issue when RBAC annotation is used on CDI beans and method that is invoked from IO thread return "something" in a synchronous manner. While it works in certain situations (if authentication happen further up the stream and current identity association has been intentionally set; in short, that's rare), it seems dodgy and we should warn users. See also #23547 (comment).