Ok, here is the scenario
new user is created and sent an email to which comes back to the site where the user is asked to rest their password. At this ount in time ijust show the password and confirm password field which is great.
The user adds a password and types in the confirm password then... I go to the same page this time telling the user that they need to change their password because the administrator wants the user to reset their password on the first login, and now it shows the 3 fields original password the new and confirm password field.
this issue is the user has and as part of the email process has changed their password on the first login and there is no need to repeat the process immediately after logging and changing the password via the email link.
I haven't looked at the code yet and was wondering if anyone already had a solution.
thanks
Comments
Comment #1
erikwebb commentedAre you saying this is happening immediately one after the other?
- User creates initial password, attempts to navigate to another page, another change is forced
Or that this may happen at their next login?
- User creates initial password, logs out or leaves the site, on next login another change is forced
Comment #2
chaloum commentedYes it happens imediatly in succession one after the other it asks you to change the password then imediatly asks again event though the first time it said the change had been saved.
The chage password is actually saved so the second time you have to use the password that was entered in the first loop.
Comment #3
erikwebb commentedComment #4
erikwebb commentedI think this might actually be solved indirectly by #1452280: Force password change broken for 'administrators'. Could you confirm?
Comment #5
aohrvetpv commentedThe redirection back to the user-edit page in the last step is the same as without the Password Policy module installed for the same account settings. So if you think it is a problem that the user is redirected back to the user-edit page after setting their password, it would seem to be a core problem, not a Password Policy problem.
Please re-open the issue with clarification if you think this is a problem that does not also occur without Password Policy installed.