[Security] more defensive PasswordMigratingListener #39263
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposed fix makes
PasswordMigratingListener
code more robust. It should handle Passports which does not contain anUserBadge
, as it is not enforced byUserPassportInterface
. Developers should be free to implement different passports with different badges (as I did on my own project), and it shouldn't lead to a crash in frameworkland.The issue became apparent in 5.2.0 exactly, as
PasswordMigratingListener
is now called in (almost) every login, asPasswordUpgradeBadge
is automatically added.