• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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