What have others been doing to prevent this problem? We have run into this problem at a site where a rogue user tried logging into EEM using the EiamAdmin credentials (which he didn't have), and successfully managed to lock the account.
I am contacting CA support to see if there's a way to not have the account locked out after unsuccessful attempts, because there are a number of side effects to it, but wanted to check if there were others who ran into this situation before and had some solution to NOT getting the account locked.
What we do with the rogue user is standard so lets not discuss that.
one thing is to NOT let them know where eEM is loaded ..
EiamAdmin lock out is temporary; it automatically gets unlocked after 3 minutes I believe.
Thanks Chandru, is there a way to not let it get locked out at all?
I don't think to prevent it from getting locked out, the intention of locking it for just couple of minutes is to stop the user from doing what he is doing.
Is there a impact you see with this lock out?