Manage Learn to apply best practices and optimize your operations.

Allowing one database to access another secure database

Allowing one database to access another secure database


You have a database with lots of sensitive information called SecureDB. You do not want to allow users to access the database, so LocalDomainServers and an admin group have only read access to the database.

Users can access a different database, called UserDB, on the same server.

The problem is that you need the users, from UserDB to have the ability to run a manual agent to pull some information from SecureDB.


There is an undocumented ACL trick in Notes that can allow this access smoothly. You can add the replica ID of UserDB to the ACL of SecureDB (include all 32 characters and the colon in the middle). This allows an agent from UserDB, regardless of who triggers it, to have the ability to pull information from SecureDB.

This was last published in August 2000

Dig Deeper on Domino Resources - Part 2

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.




  • iSeries tutorials's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...