Skip to content

Remove LazyCsrfTokenRepository #13196

Open
Listed in
Open
@jzheaux

Description

@jzheaux
Contributor

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.

Activity

added
in: webAn issue in web modules (web, webmvc)
type: breaks-passivityA change that breaks passivity with the previous release
and removed on May 18, 2023
ASDasd341

ASDasd341 commented on Aug 5, 2023

@ASDasd341

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    in: webAn issue in web modules (web, webmvc)type: breaks-passivityA change that breaks passivity with the previous releasetype: enhancementA general enhancement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @jzheaux@ASDasd341

        Issue actions

          Remove LazyCsrfTokenRepository · Issue #13196 · spring-projects/spring-security