SSOCONFIG

check your $LAWDIR/system/install.cfg file for the

SSO_CONF_PASSWORD

attribute

I entered the same password as in the install.cfg but it still says it is not valid password.

try ssoconfig -? and see if ssoconfig -p is supported on your system. That should enable you to reset it.

Jeff, thanks for your response. I tried the ssoconfig -p [CODE], but you need to enter your code, right? And the code is supposed coming from your email when you use ssoconfig -r ? Is there any way?

I've never used it, but it's in the doucmentation "Lawson Administration: Resources and Security Version 9.0" - ssoconfig -p on page 193 does not require the [CODE] which is optional syntax. It seems the document is inaccurate as the code should be an option. I would open a support ticket with Lawson.

Thanks Jeff! I asked the lawson support. Since the recipient (according to install.cfg) never receive the recovery email, the laswon support also wanted me to check what is the email address specified in authen.dat under lawdir\system. So, it is not the same email address as in the install.cfg. It was sent to another person other than in the install.cfg. unfortunately, the person is out of office for 3 weeks. I need to wait, and maybe he knows the password, or if I have to change the password, I still need to use the -r and it will sent out the encrypted password, it is very ugly and you need to type in one by one.(I tested it on other server)

I have Lawson v901 on-prem running on UNIX AIX 7.1.
I would like to find my SSOCONFIG settings, we are planning to move to a new domain.
We just ran the SSOCONFIG -c and the following is what we got:

Please enter the password used for Lawson security utilities:
Got exception: Trust between TrustedUtil and sso.dll was broken. Please check bi
naries for authenticity.
Stack Trace :
com.lawson.security.authen.SecurityAuthenException: Trust between TrustedUtil an
d sso.dll was broken. Please check binaries for authenticity.
        at com.lawson.security.interfaces.GeneralLawsonSecurityException.(
GeneralLawsonSecurityException.java:60)
        at com.lawson.security.authen.SecurityAuthenException.(SecurityAut
henException.java:87)
        at com.lawson.security.authen.TrustedUtil.rdWNE(TrustedUtil.java:129)
        at com.lawson.security.authen.SSOConfig.getPwd(SSOConfig.java:544)
        at com.lawson.security.authen.SSOConfig.processInteractiveConfiguration(
SSOConfig.java:377)
        at com.lawson.security.authen.SSOConfig.main(SSOConfig.java:311)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at com.lawson.rdtech.command.main.Main.exec(Main.java:352)
        at com.lawson.rdtech.command.main.Main.main(Main.java:46)

 

 

Andy,
This is a really old thread. You may not get the responses you need without a new thread.

Be that as it may, your issue could be any of the following:
1) permissions on the binaries and or config files (look into permsmaint)
2) a bug from an update. Some releases were broken when it came to this. I don’t believe anyone has access to the V9.0.1 Environment patches, unless they are saved off

In any case, you may need to access the ldap directly to get the info you need. But updating it will be an issue