-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Security] Cannot have a custom authenticator which implements EventSubscriberInterface
#59071
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
Comments
I ran into the same issue when trying to upgrade to 7.2.0. My workaround was to pull the event subscriber portions into their own class. |
Thanks for your reply. It is a possibility. But I wonder if it is a bug. @MatTheCat, do you think it is? Thanks |
Looks like a bug yes 😅 I guess this is not the only case of a service decorated by two different |
Hi @MatTheCat, Yes, it works with this fix 👍 Thank you 🙂 |
…their traceable version (MatTheCat) This PR was squashed before being merged into the 7.2 branch. Discussion ---------- [SecurityBundle] Do not replace authenticators service by their traceable version | Q | A | ------------- | --- | Branch? | 7.2 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #59071, fix #59091 | License | MIT Commits ------- d44b7af [SecurityBundle] Do not replace authenticators service by their traceable version
Symfony version(s) affected
7.2.0
Description
Hi,
When I try to update from Symfony
7.1
to7.2
. I have an error on cache clear:It seems to be related to:
When I add this code on
vendor/symfony/security-bundle/DependencyInjection/SecurityExtension.php
line 646:It works.
Is it an issue? Why I can't implement
EventSubscriberInterface
anymore?Thanks,
Mickaël
How to reproduce
I created a repository: https://github.com/misaert/test-custom-authenticator/commits/main/.
The last commit is with Symfony
7.2
. Before this, we can launchbin/console cache:clear
but with this commit, we have this error:Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: