Impact of changing QPWDLVL from 0 to 2
Dan <[email protected]> Thu, 17 May 2007 12:43:52 -0400
| Newsgroups | gmane.comp.systems.as400.security |
|---|---|
| Message-ID | <[email protected]> |
I am a non-sysadmin (P/A) on a v5r3 system. I would like to know if there is any impact from changing QPWDLVL (Password level) from 0 to 2. As a reference: 0 = User profile passwords with a length of 1-10 characters are supported. 2 = User profile passwords with a length of 1-128 characters are supported. Also, according to the security reference, when using QPWDLVL=0, the rules for specifying passwords are the same as those used for user profile names. Because our network passwords are required to use special characters, it would be nice if I could use the same password for the network and our AS/400s. But I find that I am unable to use most special characters on my AS/400 password. So, if I make a suggestion to the sysadmins to change the QPWDLVL to 2, I would like to be able to tell them that there is no impact for doing so. I.e., users will not have to change their existing passwords, and the other password-related system values still apply, and when users passwords expire, they will be able to enter any password they would otherwise have been able to when QPWDLVL=0. The *only* difference is that users *may* begin using special characters in their passwords. Hmmm, users would also need to remember that the passwords would be case-sensitive. But they need to do that now with their network passwords, so that shouldn't be a big issue. Am I on the right track with this thinking? TIA, Dan _______________________________________________ This is the Security Administration on the AS400 / iSeries (Security400) mailing list To post a message email: Security400-Zwy7GipZuJhWk0Htik3J/[email protected] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/security400 or email: Security400-request-Zwy7GipZuJhWk0Htik3J/[email protected] Before posting, please take a moment to review the archives at http://archive.midrange.com/security400.