- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Thanks for creating this issue.
I'm going through all the 8.x issues.
As the 8.x is no longer supported, I'm postponing this issue for now and need feedback as to whether or not this issue is relevant to 4.0.x.
If it is, please reopen and change the version, and make sure the issue summary is clear and complete, including concrete steps to reproduce. If it's not, please close.
If there is no response to this in a month addressing the above, it can be closed.
- 🇭🇺Hungary fox mulder
The issue still exists when using Password Policy 4.0.3 together with Generate Password 2.1.2.
Here is how to reproduce the problem:
Enable the Generate Password module with its default settings, except for one change: on the page /admin/config/people/accounts, in the "Generate Password - User Account Registration" section, set "Admin password entry" to "Admins cannot set a password when creating or editing an account." This will hide the password field on user registration form.
Set up a basic password policy with at least one constraint, such as "Password character length", requiring the password to be at least 1 character long.
Now, when an admin tries to create a new user, everything should work fine unless they accidentally use an existing username or email address. In that case, even though the generated password most likely satisfies the policy, the following error messages appear:
"The password does not satisfy the password policies."
"Password length must be at least 1 character."
These errors are misleading and suggest that the password generated by the genpass module is somehow invalid. I believe this is the same issue originally reported.