Skip to content
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

Remove LazyCsrfTokenRepository #13196

Open
Tracked by #13068
jzheaux opened this issue May 18, 2023 · 1 comment
Open
Tracked by #13068

Remove LazyCsrfTokenRepository #13196

jzheaux opened this issue May 18, 2023 · 1 comment
Labels
in: web An issue in web modules (web, webmvc) type: breaks-passivity A change that breaks passivity with the previous release type: enhancement A general enhancement

Comments

@jzheaux
Copy link
Contributor

jzheaux commented May 18, 2023

As LazyCsrfTokenRepository is deprecated, it can now be removed.

Note that a number of components use setAttribute(HttpServletResponse.class.getName(), response) to store the response for later use by LazyCsrfTokenRepository. This ticket should also remove those references.

@jzheaux jzheaux 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) type: breaks-passivity A change that breaks passivity with the previous release and removed status: waiting-for-triage An issue we've not yet triaged labels May 18, 2023
@jzheaux jzheaux mentioned this issue May 18, 2023
6 tasks
@ASDasd341
Copy link

in place of LazyCsrfTokenRepository you can use CookieCsrfTokenRepository, itprovides a more secure and efficient way to manage CSRF tokens in Spring Security.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web An issue in web modules (web, webmvc) type: breaks-passivity A change that breaks passivity with the previous release type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants