-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Backport 2.2-develop] #11409: Too many password reset requests even when disabled in settings #11435
Conversation
See #11434 (comment) for comment on change. |
@@ -27,7 +27,7 @@ class Config implements ConfigInterface | |||
/** | |||
* Configuration path to fronted area | |||
*/ | |||
const XML_PATH_FRONTED_AREA = 'customer/password/'; | |||
const XML_PATH_FRONTEND_AREA = 'customer/password/'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately we cannot rename constants even if it contained a spelling mistake before :( http://devdocs.magento.com/guides/v2.2/contributor-guide/backward-compatible-development/index.html#removing-or-renaming-constants
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could always deprecate the constant with the spelling mistake, create a new constant and use that. Then update the old constant to use the new one, I think that would work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed it would be great to get this to include the same changes with #11434 and also to update the constants so that we do not break BC.
057524e
to
84c9c91
Compare
I will put this on hold until #11434 has been merged into 2.3-develop |
Now that #11434 has been sorted can you make the same changes into the backported PRs @adrian-martinez-interactiv4 |
84c9c91
to
8e29dc7
Compare
8e29dc7
to
d06190d
Compare
… requests even when disabled in settings #11435
[EngCom] Public Pull Requests - 2.2-develop - MAGETWO-84981: Trying to get data from non existent products #12539 - MAGETWO-84979: [Backport 2.2-develop] Fix swagger-ui on instances of Magento running on a non-standard port #12541 - MAGETWO-84903: Added namespace to product videos fotorama events #12469 - MAGETWO-84862: [Backport 2.2-develop] #11409: Too many password reset requests even when disabled in settings #11435 - MAGETWO-84856: Issue 12506: Fixup typo getDispretionPath -> getDispersionPath #12507 - MAGETWO-84808: 12110: Missing cascade into attribute set deletion. #12167 - MAGETWO-83503: [2.2] - Add command to view mview state and queue #12122 - MAGETWO-80223: Fix syntax of expectException() calls #11099
When attempting to reset a customer's password via the admin, the system tells me 'Too many password reset requests' even when I have disabled the 'max wait time between password resets' in the store configuration settings.
Related with PR#11434
Description
\Magento\Security\Model\Config::getXmlPathPrefix() method fails to use the customer configuration
customer/password/
, using theadmin/security/
settings instead, when reset password is triggered from admin, due to current scope:Emulated frontend area in scope in plugin method \Magento\Security\Model\Plugin\AccountManagement::beforeInitiatePasswordReset, also fixed di.xml parameter injection that caused customer password reset requests also counting as admin user requests when emails coincide for admin user and customer.
Fixed Issues (if relevant)
Manual testing scenarios
Contribution checklist