Plesk Obsidian Default Password Strength Policy changes starting from February 18th, 2020

Follow

Comments

3 comments

  • Avatar
    Dr. Koontz

    Hello,

    This will create issues with WHMCS as discussed here.

    https://support.plesk.com/hc/en-us/articles/360009266814-Password-generated-by-WHMCS-is-rejected-in-an-attempt-to-create-a-system-user-in-Plesk

    Unfortunately some symbols that WHMCS uses are not used by Plesk.

    Those symbols are (, ), ;, [, ], ., {, }, -

    As a result, what can end up happening, and it happened often enough to be a problem, is that when the password strength in Plesk is set to Strong, and WHMCS generates a password that contains only symbols that Plesk does not recognize as special symbols, then Plesk does not recognize the password as being valid and rejects it. This causes the automatic user account creation from WHMCS to Plesk to fail.

    What I would like to know is whether or not there have been any further "internal" discussions about addressing this issue?

    Now that you are setting the default Password strength to "Strong" I think it's a good time to revisit this issue for better cross platform compatibility.

     

    kind regards,

    Dr. Koontz

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Dr. Koontz

    Thank you for sharing your experience.

    I don't the information about such discussion existence but what I will do is to deliver your feedback to the team in charge for consideration.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Dr. Koontz

    According to the information I received in WHMCS 7.9 GA (January 8th), this behavior was adjusted in WHMCS and integration should work fine out of the box.

    What WHMCS version do you use?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request