Re: How to preserve password change date

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

>Hi,
>Does anyone know a way to prevent the QSYSUPWD api from changing the password
>change date? or maybe a way to reset the change date to its original value?
>I want to temporarily change a users password and then restore it back using
>the QSYRUPWD and QSYSUPWD API's. But I don't want the originalpassword change
>date to be lost so that the user has to keep their next change on the correct
>schedule.
>
>Any help would be appreciated,
>Thanks
>-Paul Jackson, Costco Wholesale, Issaquah, WA



There is NO reason for a Security Officer to know a user's password
("...and then restore it back...").  A password belongs to the user and
only to the user.  I -want- a user to know if anyone else has been using
their profile and password!

If you need to perform some function as a user, create a user profile for
yourself.  You'll be using all the checks and balances built into your
applications, and protect yourself from those 'oops' moments.

I try to forget the passwords I assign as soon as I do so.  If I ever get
the time, I'm going to revise our 'CRTUSR' command to set things up so the
password I assign is set to expire, so the user -has- to create a password
that is known by 1 person only!

As far as the change date being on a schedule... there's really no need to
keep everyone's password change date the same.  We try to spread them out,
so we don't get a wave of calls every 60 days + 1 when everyone calls to
say, "I just changed my password and I can't remember it."

--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---