LDAP Bind to Corporate AD for Authentication

unknown

If you currently use LDAP Bind from Lawson to AD please share how you handle these situations.
Name changes - if someone gets married or divorced and changes their login name. How do you manage the audit trail and maintain the history or jobs for that user?

If there is a network ID kwilliams = kathy williams and Kathy leaves and a Karen Williams starts and network ID is reused kwilliams Is there a way to show the difference or will the system pick up history from the last kwilliams?

Is there a cross walk where the Lawson LDAP uses employee # and can map to AD using a corporate Network ID?

Any help or information is appreciated as these are questions in making the decision moving forward with LDAP Bind.

moellerg

We use employee id as our login to lawson.. we have this included in a different field in AD. As long as the field types are the same as cn, it should work.
For instance: My network login is doej and we have employee number stored in the wWWHomePage field in our corporate AD, so I can log in to lawson using my employee number and my corporate AD password. (As long as you bind Lawson to the wWWHomePage field instead of cn, or whatever it tells you in the instructions).

Of course, this causes a little extra work on our AD person when employees quit and then return. She likes to assign them brand new AD record ids and sometimes forgets to remove the employee number from the old wWWHomePage field. The user cannot log into Lawson, because it doesn't know which record to associate with.