Travis failures seems unrelated to this changes.

Hi @smoench! I'm interested to know how you use this interactive login event and why you don't use one of the new login events.

While writing the new system, we discussed the interactive event and found out that it was very inconsistent (and almost to the point of becoming unusable): #33558 (comment) That's why I intentionally left it out and only dispatched it for legacy reasons. My idea was to deprecate this event in 5.3/5.4 (whenever we remove the experimental state from the new system). However, it would be interesting to see if that would result in missing functionality.

Hi @wouterj!

I was migrating from a Guard-Authenticator to the new approach. One of my tests has failed because there is a Listener listens on Symfony\Component\Security\Http\SecurityEvents::INTERACTIVE_LOGIN. As the documentation says no word about how to act on interactive logins I was debugging the code. Then I was wondering why the AuthenticatorManager dispatches the interactive login event but my listener doesn't get called. I thought this might be a bug and I provided this PR.

Meanwhile I could migrate my listener to the new LoginSuccessEvent. Thanks!

IHMO the dispatch of Symfony\Component\Security\Http\SecurityEvents::INTERACTIVE_LOGIN could be safely removed as the event is not allowed for bubbling and listeners could only be added via a compiler pass to the firewalls event dispatcher.