We are looking to change the Lawson user password and I would like to know if anyone else has done this and where within the system I need to make sure I set this new password.

What OS are you on?

This is a question that you have do some research to figure out. a lot fo clients have the Lawson user run many processes so it can vary.

For starters:

1) You'll need to change the pass in the Database file (MICROSOFT, ORACLE, ..) in $LAWDIR/<productline>

2) Depending on your version of environment, you'll have to change the processflow config if it uses the user lawson in any way.

3) Any other custom script the password is hardcoded in

4) If you're using DataStage/Mercator and making DB connections using the Lawson user ..


Keep in mind, most of the above should NOT be done by the lawson user at the first place but lots of clients seem to take that route.

We initially did not have people changing LID passwords because we were on Unix and when using Desktop Client Logon people couldn't see that their passwords were going to be expired.

However, I found a script that runs everyday to check whether or not it's time for them to check their passwords, and then sends an email notifying how do to it; One issue that came up afterwards though was that we have users in two separate domains, i.e. domain1.com and domain2.com for their emails and they I resolved this was to send an email to their account on the Lawson application server but it had ".forward" file on their user account to forward it to their correct email address.

Also, we created a new token in the menu system that runs the command line directive to change their password from Desktop Client Logon.

But as Tan said it depends on your system...

Hmm, wait, you ARE asking about the password of the user Lawson itself right? Not just any Lawson user. I mean the user whose name is Lawson. You know, the guy on first base, who's the guy on first base.

Nowhere in the off-the-shelf Lawson system is there any restriction on changing the lawson user password - HOWEVER.........

If you've written scripts, etc.. where t e password is embedded then you'll need to find and change all those occurrences. On Unix try:

find / -type f -exec grep <current_lawson_password> {} \; 2> /dev/null

which will check every file that 'lawson' has access to, anywhere on the system, to see if it contains the curent lawson password.

g'luck!

Oh, maybe I miss read it; :blink:

We are a windows shop, I know, don't shoot the messanger. Thanks for all the replies. I know we have the DB, the SSOP, the Services and any scripts that may have been written, but I'm not sure of any other services that may have been setup using the Lawson user name, you know, the one of first base, the Lawson user itself, not all lawson users. :D