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 first published in August 2000

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
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
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.