-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Smarter HttpSession Access #6125
Comments
@rwinch I like to work on this issue, could I? |
Thanks @Daniel69! The issue is yours 😄 This will likely be a larger issue and a bit tricky since a lot of the architecture relies on the assumption that the I think we should start by finding the places where the HttpSession is resolved and how we can minimize it's access. I believe this is just at the authorization layer, but may be mistaken. As for the authorization layer, I think we want to change it to be similar to how the WebFlux authorization APIs are. The API would not require the |
@rwinch when you say
You mean that we would resolve the Authentication and therefore the HttpSession in a lazy way ? |
I mean that right now the AccessDecisionManager takes the To get around this we would need to create an API similar to ReactiveAuthorizationManager which didn't take the |
Hi. Is there any progress on this one? |
Summary
For resources that are public (i.e. images, javascript, css, etc) Spring Security should in many cases be able to avoid accessing the HttpSession. This has a significant implication for applications using Spring Session.
We should make Spring Security smarter about how it accesses the HttpSession.
NOTE: We have already done this for WebSession in reactive applications
The text was updated successfully, but these errors were encountered: