• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

The password does not meet password policy requirements

W

webaus

Guest
Im getting the error

The password does not meet password policy requirements because it is not complex enough.

after migrating from a backup file from plesk 8.2 to a new install of 8.4 on windows 2008

anyone know how to resolve this error?
 
To resolve this issue you will need to turn off windows2008 password complexity check.

To do this access "administrative tools" - "Local Security Policy"
Then in this area access "Account policies" - "Password Policy" and disable the password complexity check.
 
The fact we're told to turn off password complexity so that Plesk is able to work if people add users with insufficiently complex passwords is pathetic.
Plesk should be fixed to respond correctly to user creation errors.
Also if a user creation fails, it should rollback the addition of the domain entry into the DNS configuration, which you otherwise have to manually remove before re-attempting to create the user with a correct password complexity.
Plesk should be accomodating ALL industry standard security mechanisms.
 
Password must meet complexity requirements

When I create a password for a mailbox, Plesk can save whatever.
I read this link, http://kb.odin.com/en/1742 , but it is a trivial method,
is not a good enough policy.

Do you have a more complex rules in order to save a strong password for mailboxs?

For example, like a length over 7 characters, force the use uppercase/lowercase and numbers, password history, expiration, etc. Something similar like options implemented in pam_cracklib in Linux, this is a excelent robust method

Thanks in advance
 
Back
Top