LSF LDAP to AD integrity check methods

Legacy Contributor

We are running LSF 9.009 bound to AD (ADAM) and run automated processes to provision and delete user accounts for S3 / EMSS (LOADUSERS). We have had many instances where the Lawson LDAP records got corrupted or orphaned requiring tedious investigation and editing with JXplorer. We are looking for a way to validate the the user entries in LDAP vs. what is currently active in AD (or vice versa) in order to stay on top of this both from an integrity and user licensing standpoint. The only method I have seen is manually dumping the entries from both subsystems and comparing the entries. Is anyone doing this in an automated fashion and what methods or tools are you using? Thanks.

mlukaniuk

We have an automated process to send our AD file to our UNIX box each night. Then we have processflows that read that file and our EMPLOYEE table to either add, delete or change users in Lawson Security depending on the scenarios. We've never had an issue with orphaned or corrupted records in LDAP by utilizing processflow to add/delete records in Lawson Security. We are on LSF 9.0.1.9, but also used this process when we were on 9.0.0.