-
Notifications
You must be signed in to change notification settings - Fork 6k
Sorting in AuthorizationAdvisorProxyFactory should be thread-safe #16834
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @ngocnhan-tran1996 for the PR! I've left some feedback inline.
...java/org/springframework/security/authorization/method/AuthorizationAdvisorProxyFactory.java
Show resolved
Hide resolved
...t/java/org/springframework/security/authorization/AuthorizationAdvisorProxyFactoryTests.java
Outdated
Show resolved
Hide resolved
Additionally, will you please rebase this on |
bc75585
to
0d7762d
Compare
SmartInitializingSingleton
for preventing ConcurrentModificationException
In order to make so that authorization advisors are sorted only one time and also as part of the configuration lifecycle, AuthorizationAdvisorProxyFactory now implements SmartInitializingBean. Closes spring-projectsgh-16819 Signed-off-by: Tran Ngoc Nhan <ngocnhan.tran1996@gmail.com>
This commit ensures that the default advisors and added advisors are sorted in the event that this component is not being published as a Spring bean. Issue spring-projectsgh-16819
SmartInitializingSingleton
for preventing ConcurrentModificationException
Thanks for the quick turnaround on this PR, @ngocnhan-tran1996! I added a polish commit to take care of scenarios where |
Closes gh-16819