Re: Disabled Userids

In the July 2006 issue of System iNews there was an article "Watching for
Messages Made Easy" which monitored for a specific user profile being
disabled due to the number of invalid password attempts, and then
re-enabling that specific user profile. The article provided examples in
CL, RPG, COBOL, and C. The article is based on the V5R4 message watch
capability of i5/OS.

Bruce Vining




"Jim Franz" <franz400@xxxxxxxxxxxx>
Sent by: security400-bounces@xxxxxxxxxxxx
05/09/2007 08:23 AM
Please respond to
Security Administration on the AS400 / iSeries <security400@xxxxxxxxxxxx>


To
"Security Administration on the AS400 / iSeries"
<security400@xxxxxxxxxxxx>
cc

Subject
Re: [Security400] Disabled Userids






The system value rules for # times bad password and what action
are global. But you can in the profile set this "batch-only" profile
to not expire to avoid an expire problem.
Set password to expired . . . . *NO
If it is "batch-only", then how did you hit this problem?
jim

----- Original Message -----
From: "Neeland, Steve" <Steve.Neeland@xxxxxxxxxxxxxx>
To: "Security Administration on the AS400 / iSeries"
<security400@xxxxxxxxxxxx>
Sent: Wednesday, May 09, 2007 9:14 AM
Subject: [Security400] Disabled Userids

Is anyone aware if a way exists to exempt a userid profile from
switching to a *DISABLED status when too many invalid passwords may be
entered? We have some special userids used for batch-only applications,
and if they happened to get disabled the applications would return
abends.

Thanks!
Steve

_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400)

mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.