RE: Preventing user profile lockout

[Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>]

If QSYSMSG exists, security sensitive messages are not send to QSYSOPR.  If
QSYSMSG does NOT exist, then they are sent to QSYSOPR.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com



                                                                           
             Chris Bipes                                                   
             <chris.bipes@cros                                             
             s-check.com>                                               To 
             Sent by:                  "'Midrange Systems Technical        
             midrange-l-bounce         Discussion'"                        
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             03/21/2005 11:42                                      Subject 
             AM                        RE: Preventing user profile lockout 
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




Messages are logged to QSYSOPR and/or QSYSMSG for account lockouts.  You
can
monitor these message queues and take the appropriate action which should
include notifying management and logging the occurrence.

Chris Bipes

-----Original Message-----

I have a requirement to prevent certain service/connection accounts from
being locked out - for example due to password validation errors. This
is to prevent the profiles being deliberately locked out as part of a
denial of service attack.

We do not want to set QMAXSIGN to *NOMAX as this applies at a system,
rather than an individual profile level.

Does anyone know of a way to do this? Is there an exit point we can hook
into when a user profile is disabled and use this either to stop the
profile from being disabled or re-enable the profile? Is there a way to
override this system value at an individual user profile level?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.