-
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
Add SecurityContextHolderFilter #9635
Labels
Milestone
Comments
rwinch
added
status: waiting-for-triage
An issue we've not yet triaged
type: enhancement
A general enhancement
in: web
An issue in web modules (web, webmvc)
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Apr 13, 2021
3 tasks
rwinch
added a commit
that referenced
this issue
Mar 11, 2022
Extract out method in preparation for adding SecurityContextHolderFilter configuration. Issue gh-9635
rwinch
added a commit
that referenced
this issue
Mar 11, 2022
rwinch
added a commit
that referenced
this issue
Mar 12, 2022
Extract out method in preparation for adding SecurityContextHolderFilter configuration. Issue gh-9635
rwinch
added a commit
that referenced
this issue
Mar 12, 2022
rwinch
added a commit
that referenced
this issue
Mar 12, 2022
rwinch
added a commit
that referenced
this issue
Apr 13, 2022
rwinch
added a commit
that referenced
this issue
Apr 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We should add a
SecurityContextHolderFilter
that loads theSecurityContext
from the request. It will not automatically save the SecurityContext. Using this mechanism requires explicitly saving the SecurityContext rather than just setting the SecurityContextHolder. We also want to consider a simplified API to SecurityContextRepository.loadContext(HttpRequestResponseHolder) so that users do not need to worry about replacing the request/response. Perhaps just adding a default method to SecurityContextRepository.loadContext(HttpServletRequest,HttpServletResponse)Related gh-9634 gh-10947
The text was updated successfully, but these errors were encountered: