Background
PasswordReset::isBlocked checks for global blocks separately, and decides the user is blocked if ::appliesToPasswordReset returns true.
::appliesToPasswordReset never returns true for a GlobalBlock, so a global block alone does not block password reset (see appliesToPasswordReset definitions and isCreateAccountBlocked usage).
Additionally, after T257701: Add global blocks into CompositeBlocks rather than treating them separately, global blocks would not need to be checked separately anyway.
Acceptance criteria
- PasswordReset::isBlocked no longer checks separately for global blocks.
Notes
Related question: Local blocks made by the GlobalBlocking extension do block password reset, by blocking account creation (example). Should global blocks block password reset and account creation? If so, this can be filed in a follow-up task and worked on separately.