• Search Forums
    Advanced Search
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

LAWSON db user account lock issues

 6 Replies
 0 Subscribed to this topic
 28 Subscribed to this forum
Sort:
Author
Messages
Manjula
New Member
Posts: 3
New Member
4/29/2011 3:12 PM
We had an issue with the lawson user's db account getting locked. Users were unable to get into Lawson. On looking at ladb.log, I saw that the Lawson user's account was locked. As a DBA I had NOT gone in and locked this user's account.

Has anyone encountered this? Why and how would this happen?

Also, Lawson recommends that the owner (lawson) should have DBA privs. I plan to revoke this privilege from the user? Any repurcussions?
EricS
Veteran Member
Posts: 80
Veteran Member
4/29/2011 3:51 PM
What OS and Database are you using? From an AIX and Oracle perspective, that's all a bad idea. You would be better off trying to figure out who entered the password incorrectly enough times that they locked the lawson account. And make clear to them what a terminally stupid idea that was. Just my opinion . . .
Manjula
New Member
Posts: 3
New Member
4/29/2011 4:15 PM
I agree... This is AIX & Oracle 10g. The only way an account could get locked was if someone entered the password wrong incorrectly or if the DBA locked the account. The second did not happen, so I think the first many have happened. I was trying to find out if something happened within the application to cause this.
EricS
Veteran Member
Posts: 80
Veteran Member
4/29/2011 4:32 PM
I can't think of any way the back office application could do this. If someone was installing MSCM and used the wrong password in the properties file, I could see that happening. Was it the AIX account that locked or the Oracle login?
Manjula
New Member
Posts: 3
New Member
4/29/2011 4:36 PM
The Oracle login was locked.
EricS
Veteran Member
Posts: 80
Veteran Member
4/29/2011 6:30 PM
Make sure your $LAWDIR/prod_line/ORACLE file is locked down. If anyone uses LID they can get to it, and that's where the passwords are stored. Not the brightest move on Lawson's part, but it is what it is. I'd like to see it moved, or at least encrypted. Check when the last time it was updated. If it was around the time of your lock out, you have the how. Next find the who.
Scooby
Basic Member
Posts: 13
Basic Member
5/1/2011 1:33 PM
EricS. Changing the file to 400/lawson:lawson (read only to the lawson user) passes the requirements of almost all Audits.

Alternatively you could put the Password in LS as a Database Identity which would then secure it to your wishes.