Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[SecurityBundle] Link UserProviderListener to correct firewall dispatcher#41509
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
nicolas-grekas commentedJun 2, 2021
Can you please add a test case if possible? |
79d3ab1 tod65695dCompareMatth-- commentedJun 2, 2021 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@nicolas-grekas I added some functional tests (Feel like this was the better way to get failing tests first). Do you have a suggestion to fix the Travis ci bugs? I feel like it used the Symfony 5.4 branch to run tests against. |
d65695d to0a713f2Comparederrabus commentedJun 2, 2021
I'd say, the Travis failure is unrelated to your changes. |
src/Symfony/Bundle/SecurityBundle/DependencyInjection/SecurityExtension.phpShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
0a713f2 to46bdeb8Comparenicolas-grekas commentedJun 3, 2021
Thank you@Matth--. |
Uh oh!
There was an error while loading.Please reload this page.
When using the new AuthenticationManager, an incorrect UserProvider could be attached to the UserBadge when having multiple providers defined in
security.yaml.The
UserProviderListenerwas tagged to the global event dispatcher instead of the dispatcher for the specific firewall.