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
new security authenticator fails #37033
Comments
Thanks for testing the new system! Can you please show some context (configuration of |
@wouterj i updated the issue with a link to the minimal project |
Thanks for your quick response! I've submitted a fix: #37047 I'm amazed that I've always tested the new system in a Symfony app with CSRF enabled 😄 |
… CSRF is available (wouterj) This PR was merged into the 5.1 branch. Discussion ---------- [SecurityBundle] Only register CSRF protection listener if CSRF is available | Q | A | ------------- | --- | Branch? | 5.1 | Bug fix? | yes | New feature? | no | Deprecations? | yes | Tickets | Fix #37033 | License | MIT | Doc PR | - I know we're not allowed to add new deprecations in already released versions. However, I don't think anyone is using SecurityBundle's compiler passes except from Symfony itself - so I don't think anyone is affected by this deprecation. The alternatives would be: * Add a new compiler pass in 5.1 that conditionally registers the CSRF listener * Do this exact change in 5.2 and... * accept a `null` argument in the listener for 5.1 * or add this to the `RegisterCsrfTokenClearingLogoutHandlerPass` class in 5.1 Commits ------- 2d738b3 Only register CSRF protection listener if CSRF is available
Strange, but I still get:
in Symfony |
please open a new issue and provide a small example application that allows to reproduce it |
Symfony version(s) affected: 5.1
Description
after enabled enable_authenticator_manager: true i got The service "security.listener.csrf_protection" has a dependency on a non-existent service "security.csrf.token_manager".
Minimal project with issue https://github.com/bitgandtter/sf-security
The text was updated successfully, but these errors were encountered: