-
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
Prepare Request Matching for Spring Framework Changes #16417
Comments
Hi, @jzheaux, can I work on this? I'd want to start with adding |
Hi, @evgeniycheban, thanks for volunteering! Some of this is already addressed in a draft PR, so allow me to clean that up first so it's clear what work remains. I'll report back here when that's ready, and then we can divvy out the remaining work. |
@evgeniycheban, if you don't mind following the draft PR while I'm gathering feedback for it, #16500 and #16501 are ready to begin work on. |
Ensure that the appropriate HTTP Method is specified in tests Issue gh-16417
To simplify migration, the filter's setter methods still use AntPathRequestMatcher. Users can call the equivalent RequestMatcher setter methods to opt-in to the change early. Issue gh-16417
Thanks again, @evgeniycheban and @pat-mccusker for your contributions! We should now be ready when Spring Framework removes |
In future versions of Spring Security, we should move away from
PathMatcher
(used byAntPathRequestMatcher
) andHandlerMappingIntrospector
(used byMvcRequestMatcher
) as they are deprecated Spring Framework 7.0 M1.This will also assist with efforts to simplify construction of path-based
RequestMatcher
s.CasAuthenticationFilter
fromAntPathRequestMatcher
SwitchUserFilter
fromAntPathRequestMatcher
OAuth2LoginBeanDefinitionParser
fromAntPathRequestMatcher
The text was updated successfully, but these errors were encountered: