A Forum reader recently asked:
"I have someone coming in this week to update the name, title, phone number, etc., in ConsoleOne so our GroupWise address book more accurately reflects our current user community. I have often set file rights for users but have never had the need to set edit-only rights that would allow for updating but not deleting users. What is the easiest way to go about doing something like that? I certainly do not want to give him full admin rights to the tree."
And here's the response from David Gersic ...
Give this person the ACLs in the directory that they need. In this case, they need to be able to read and write the Given Name, Surname, Full Name, Title, and Telephone Number attributes - maybe a few more.
Then he'll have to make sure that the GroupWise process that updates the address book from eDirectory actually does what it's supposed to, unless he also wants to give this clerical person the GroupWise admin utilities and rights within GroupWise to make these changes.
Assuming you give them ACLs to allow them to access these attributes in eDirectory, how are you going to get the changes in to GroupWise?
It's a trick question, somewhat, as there are several possible answers.
- You can give this person sufficient rights in eDirectory, plus give them rights to administer GroupWise. Then with the GroupWise administration utilities (ConsoleOne snap-ins) they can make the changes directly.
- You can have them update eDirectory only and use GroupWise's data import/sync process to update the GroupWise address book from the directory.
- You can run the IDM driver for GroupWise, which will automatically sync the eDirectory changes into the GroupWise database in real time.
Peter Kuo adds:
I'd have this person create an LDIF with the proper info, and then the administrator can import the file ... no rights required!
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.