SSOCONFIG -c

 14 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Mick
Veteran Member Send Private Message
Posts: 82
Veteran Member
When I try and launch ssoconfig -c I'm getting ssoconfig is secured.
It is not letting me type the password for ssoconfig.
How can I get to ssoconfig?
Thank you
George Graham
Veteran Member Send Private Message
Posts: 201
Veteran Member
Are you sure you have the correct password? If it has not been changed since the install you can find it in your install log.
Mick
Veteran Member Send Private Message
Posts: 82
Veteran Member
Well I'm not getting that far to be honest. I simply type ssoconfig -c and receive that message.
I don't get the option to enter the password.
should I type it with ssoconfig -c and the password?
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
Mick is correct.

The issue is the LAWDIR/system/lase*.log.lck files. Delete those and run 'ssoconfig' as 'lawson' or 'root' and you'll be fine.
NOTE: If the system is up, the lase_server_[01]*.log.lck files should not be removed

IF you want to run it as someone else, then you'll need to grant it via security.

Kwane
Mick
Veteran Member Send Private Message
Posts: 82
Veteran Member
Kwane, can I ask...
should I stop all or stop everything then delete?
What I am seeing is this:
2/19/2013 lase_server_0_0.log.lck. So I delete that file?once I bring it down?
stoplaw?

Thank you
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
No need to do that. If the 'lase_server_0_0.log.lck' file is the *only* one you're seeing, then that's not your issue.

ssoconfig -c should not check security (either LAUA or LS) if you are 'lawson' or 'root', but only prompt for the ssoconfig password.
If you're trying to run this as anyone else, then you have to grant it via security. if you don't see it in security to grant, you'll have to add it via tokendef.

Kwane
Mick
Veteran Member Send Private Message
Posts: 82
Veteran Member
Kwane,
i have two of those files.
It looks like this:
2/15 lase_server_0_0.log
2/19. lase_server_0_0.log.lck

2/15 lase_server_1_0.log.lck
2/16. lase_server_1_0.log.lck

will that work to delete those?
Mick
Veteran Member Send Private Message
Posts: 82
Veteran Member
Kwane,
WHen I run it as lawson i'm receiving these messages.
Exception in thread 'main' java.lang.unsatisfiedLinkerror: sso (not found in java.library.path)
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
Mick,
No. Those are always there. So the stale lock file shouldn't be your issue. Who are you running 'ssoconfig' logged in as anyway? Also is either or both LAUA and LS security enabled?

Kwane
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
Also make sure 'lase' is running. Run 'lase' from the command prompt and see what the result is.
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
That unsatlink error is an issue. You have some sort of classpath issue or missing library. Check your PATHs set in the session closely.
Mick
Veteran Member Send Private Message
Posts: 82
Veteran Member
Kawne,
ok... when I ran the . cv then used the lawson user I was able to login to ssoconfig.
Now on the other server (we are horizontally scaled) if I use . cv or not using lawson user.
I'm getting.
java.io.FileNotFoundException: $LAWDIR/system/ .ssobackup/authen.dat (permission denied)
at.....
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
Mick,
That may be legitimate. If the perms on authen.dat are tight, then any user who is not 'lawson' nor 'root' may not have perms. To tell you exactly, I'd have to see a bit more specific info from your exact setup.

Feel free to call
Kwane
505-433-7744
TJ Mann
Veteran Member Send Private Message
Posts: 44
Veteran Member
i ran into this issue, and added SuperAdminRole, and i was able to run ssoconfig -c
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
This turned out to be minor filesystem permissions issues related to an issue with an earlier attempt to run the revert. I spoke to mick, and we resolved it in short order.