LDAPBIND

Sorry if this has been discussed before, but we are attemping our Lawson/AD bind this coming weekend. Yes, I know we are behind the times. Anyway are there any 'gotchas' we should know about. We have done the ldapbind on two of our test Lawson environments and they seemed to go thru okay. Just a little anxious about this one.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

always backup your Lawson LDAP before doing work. ldapbind, and answer a few questions, and you are good to go. if you are not ldapbind yet, in LSA | manage identity, you don't have SSOP_BIND. after ldapbind, you should see it there.

todd-brown

Good, thanks. Also how does this bind affect Admin users that use recdef, jobdef, etc thru LID. We have a few users that still have an laua account just for this purpose

asztudenyak

LID users are still LID users. We have LDAP and I don't think there was any impact on LID users. I mean, you have to continue to use LID for system admin stuff, so I would not expect a problem.

unknown

ldapbind is a command that should be used very carefully. Do exactly what you are supposed to do, and nothing else. Above all, don't abort half-way through because you were "just trying it out". It will leave your LDAP install in very bad condition. (I got this knowledge from my own very costly experience.) When ldapbind is properly done, it's a joy to see it work well.

todd-brown

Good to know.. Thanks How many users did you have in Lawson when you did your bind, and how long did the bind take?

unknown

Since that first encounter, I've done ldapbind for many various sized LDAP's, from under a hundred users to many thousands. it always runs very fast, within seconds. This is an old-fashioned data processing style utility without any fat data overhead like voice or video. So the longest part of running ldapbind is setting the commands up correctly.

Copyright © 2025 Infor. All rights reserved.