× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



John Candidi wrote:
We have very loose password requirements and we want to tighten
them a little by requiring a certain length and certain
characters. If we make that change today, what happens when a
user signs on with a password that doesn't fall within those
requirements? Are they prompted to change their password at that
time or does the system just not allow them to sign on? And when
does that change take affect?


The password complexity requirements apply to CHGPWD. Thus although the changes take effect immediately, there is no impact to users with existing passwords; no forced prompt for change, and they can signon without any impacts. That is, users will continue generally unaffected. To force an effect, then issue CHGUSRPRF PWDEXP(*YES) for each user for which the change should be made immediately; i.e. force them to change their password due to its [forced] expiration.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.