User Auto-Disable Handling

[Mike Wills <koldark@xxxxxxxxx>]

Sorry for the cross-post, but this is a more appropriate place.

Is there an exit point for user validation at sign-on? We are looking into
the posibility of locking a sepecific user(s) after a number of invalid
logons differently than all the other users. I see I can't do this through
their profile alone, so I am hoping I can do this through an exit point. The
reason we are looking into this is for a scenario like this.

* Mission critical PC application uses iSeries as a DB via ODBC.
* To keep good security, system is told to lock account after x number of
invalid logons.
* This happens to the account that the PC application uses to connect to
iSeries via ODBC, thus locking account and any new connections to the
system.
* Mission critical PC application breaks because account is locked.

Now in this scenario, there was another problem of using a user account for
this connection, but that was corrected. We are worried about in the future
with the what-if scenario.

How do we prevent that account from becoming locked? This is assuming that
the the user account has a strong password and cannot easily be hacked. Or
better yet, what policies do you have in place so this situation doesn't
happen?

--
Mike Wills
koldark@xxxxxxxxx
http://mikewills.name
Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.

"There are 10 types of people in the world: those who understand binary, and
those who don't." -Unknown