Guide to Correct & Proper ACL in Domino Directory

We have a manager who was sitting inside our network, and now he is in handling one of our site office. So just last week we are configuring his machine to use LN remotely using a remote client software… we allow our remote users to replicate our domino directory… during replication, we noticed that a lot of old entries, especially users who left the company (we deleted already from our Domino directory) came back on our listing which was very frustrating because we had to double check again our inventory… and we have to remove them right away… it was a bloody task we had… I am still trying to figure out why this thing happened

I noticed that our default ACL, everybody has right to replicate…

I need somebody to guide me on what is the proper, safe and correct ACL that i will be assigning our users on our Domino Directory in a technical point of view…

Putting in mind that we need to allow our remote users to replicate our domino directory… is there a recommended and safest way to do it instead of using and replicating our directory?

I am still a newbie in terms of administering and we are still on the process of fine tuning our entire setup…

any help would be appreciated…

=)

Subject: Guide to Correct & Proper ACL in Domino Directory

Reader should be fine for default ACL for NAB with replicat & copy. This will allow users to only read/replicate not to add anything in NAB

May be ur manager has higher access to NAB through a group in NAB ACL that is why he was able to add old docs to NAB on server when replicated. Also on users PC u can set replication to just receive, no need to send

I assume that u r replicating directory to users PC just for the name lookup & mobile purpose. Setup a mobile directory for that purpose & replicate it to users PC, its much more smaller

Subject: Guide to Correct & Proper ACL in Domino Directory

I need somebody to guide me on what is the proper, safe and correct ACL that i will be assigning our users on our Domino Directory in a technical point of view…

Here’s one approach to ACL organization …

Manager: Your admin server and the few trusted human administrators (e.g., LocalDomainAdmins)
Designer: Your pubnames.ntf designers (if any) who are not managers

Editor: Your domain’s servers (e.g., LocalDomainServers)

Author: Groups containing your users (e.g., */IBM)

Reader: “Outside” users/groups that need to see your directory

No Access: -Default-, Anonymous