Hello,

In my previous answer I referred to password policy: how long the password should be, how many numeric characters should be etc. The password change frequency and the change limit are not part of the password policy. So, if you want to change the password change frequency, you can make it before or after enabling long password.

In case you change the frequency from 90 to 30 after the long password has been enabled, the password policy (length of password, number of special characters, number of numeric characters etc.) will be taken into consideration when the password will be changed

Thank you!

Best regards,
Cezar

Hello,

Here are the answers:
A1. You need to restart the Enterprise Servers acting as Security Servers and the JAS servers. The Long Password feature is read by the E1 HTML instance during start-up and checks if *LPENABLE row exists in F98OWSEC
A2. The policies need to be changed after activating the Long Password. This is because after enabling the Long Password the policies will be stored in the BLOB filed of *LPENABLE row.
A3. Yes
A4. No. There is no feature which has to be enabled for long passwords for proxy/system users.
Starting with 9.2.4.3 tools release, the proxy/system users passwords may have 40 characters and it is case sensitive. So in P980001 passwords longer than 10 characters are accepted.
A5. Is not clear what you are asking. If you want to apply the long password for some of the users based on their groups, this is not possible. When enabling Long Password, all users will benefit of it.

NOTES:
1. The short passwords will still be accepted. It is not required to change the passwords after enabling Long Password feature;
2. The password policies will apply only when the password is changed by the users and they are never verified during the login process.
3. When Long Password feature is enabled, the passwords are case sensitive.
4. Once the Long Password feature is enabled, it cannot be disable and revert back to the classic short password, unless a backup of F98OWSEC is restored.

Thank you!

Best regards,
Cezar