|
Why should auditing have a problem with you "assigning" passwords. Even if you have a program to generate a password, you will still need to know what that password is so that you can inform the user. As s Savings and Loan, we are constantly audited, both internal and external, and we follow the same procedure. Someone assigns the password, with *EXPIRED. No problem what so ever. Good luck Good hunting >>> "McKay, Steve" <Steve.McKay@SouthTrust.com> 10/23/02 02:07PM >>> List - Does anyone have a CL/RPG/COBOL solution to generate "random" passwords? Auditing has a problem with me "assigning" an initial password (even if it is set to "*EXPIRED") and wants to programatically generate a password for each new user. Thanks, Steve _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
