RE: Client Access vs CAE

["Urbanek, Marty" <Marty_Urbanek@xxxxxxxxxxxx>]

Also beware, in addition to what Al said, I don't get the impression that it
is a simple matter of turning on the 128 char password option. I get the
impression that it could create total chaos if you don't plan the change
thoroughly across all the 400s in your network, because there are so many
passwords etc exchanged, that if you don't keep them in sync, a lot of
things you take for granted, like communications, could go up in smoke.
There are a couple of intermediate settings you can use for testing, so that
you can still revert back to the old way, but once you make the final
commitment to long passwords there is no turning back.

-Marty

------------------------------

Date: Thu, 31 May 2001 11:19:53 -0400
From: barsa@barsaconsulting.com
Subject: RE: Client Access vs CAE

There's a new system value for password length, QPWDLVL.  Briefly (this is
somewhat oversimplified, but good enough for this forum) there are two
choices.  Old passwords (10 characters long - non case sensitive) or new
passwords (128 characters long - case sensitive).  Unfortunately, DST/SST
now has it's own user profiles (you can create your own users too) that
have passwords that are 128 characters long, case sensitive, and expire
every 180 days.  The DST/SST user profiles have no relationship with the
OS/400 user profiles, except when you use then new LPAR API's, in which
case the passwords must match.

Al
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---