Hello,
I am doing some systems integration work for a client. We're looking at provisioning accounts to Lawson. Working with Lawson support I began looking at working directly with the ADAM tree, at their direction.
However, after reading through several posts here it seems that loadusers may be a cleaner solution. I wanted to ask a couple questions before proceeding down that road.
Does loadusers support modifying of users? For example, does an xml file passed to loadusers overwrite existing ADAM entries with new data?
The clients current verion is 9.0.0.4. Is the -u switch supported to remove users in this version? I have read conflicting info, but my best guess that this began with 9.0.0.7. Can anyone confirm? I'm guessing it's not supported on 9.0.0.4 as this switch does not show when loadusers is executed on the client's system.
Thanks very much for your time,
Chuck
Thanks for the reply Matt.
After speaking with the client it sounds like they have a bind with AD. Are there any issues I should be aware of while using loadusers under these conditions?
Will loadusers populate the tree with the appropirate password(etc) from AD? From what I've been told this is what happens when they manually add a user.
Thanks again for your help.
Thanks again Matt. You were correct, there were no issues with the AD bind. After loading in a couple test users, the client reports that the users are showing up in the RM object area, but are not showing up in the portal or the process flow admin tool. Before I go too far comparing user data...should loadusers populate the areas the client is describing? If so, do you have any ideas as to what I may be missing(attributes etc.)?
Thanks again for your time.
Best Regards,
Thanks for the reply Norm.
I had an opportunity to look at the ADAM data and loadusers is getting the info in, and I am able to log into the portal...however when I attempt to use one of the bookmarks I get:
Requester does not exist Login: username Requester: username Product Line: PD90
I tracked down the AD sec group Lawson Environment LAUA authentication, and the test user is not currently a member. In your environment, if a user is setup in the LDAP tree as a requester and a member of the LAUA group is this sufficient to get the user to show up as an active requester? I realize my client's environment may differ...I am just trying to pin down how this works.
Thanks again for helping me out.
Best Regards