Who's On?

	Membership:
	Latest: Zac Shields
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5211

	People Online:
	Visitors: 485
	Members: 0
	Total: 485

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

redo ldap bind

3 Replies

0 Subscribed to this topic

27 Subscribed to this forum

Sort:

Author

Messages

hsuhsen

Basic Member

Posts: 23

4/1/2010 8:41 PM

Hi, We need to redo our ldap bind. The original bind was done as the lawson user which is not recommended. We need to change our lawson user password but can't until the bind is redone using a different user. I know lawson does not support clients doing their own ldapbind, but my understanding is that it is not very difficult. To those of you who have done it, are there any gotchyas I should be concerned with? Is it difficult to revert to the original bind if necessary?

mark.cook

Veteran Member

Posts: 444

4/2/2010 11:19 AM

We have done the unbind/bind a few times now over the last couple years. The process was fairly simple and we did not have any issues from this process. We upgraded our AD and upgraded LSF/Apps and overall had no issues.

If you have specific questions through the process, reach out and I can try to get them answered for you

bprouty

Basic Member

Posts: 12

4/2/2010 4:16 PM

We did a ldapbind yesterday. It is not working. From the Portal screen, it looks like it is trying, but stays on the logon screen, it does not say anything. We are getting an error in $LAWDIRsystem/security_authen.log
[LDAP: error code 49 - NDS error: failed authentication (-669)]

If I try to logon with an invalid user, then it says invalid user or password

I still have my SSO_EXPORT file. I was told to set it back to that file. From what I am reading there are two ways to do it:
1- ssoconfig -l password SSO_EXPORT----.xml
2- ssoconfig -c
Manage Lawson Services
Load service and idenntify file
SSO_EXPORT------.xml

Can someone confirm that I should do either 1 or 2. Then our LDAP people will hopefully research some more to figure out what setting we have wrong and we will try the ldapbind again.

John Henley

Posts: 3353

4/2/2010 4:56 PM

Either 1 or 2 will work...they are the same command...