Encrypting new attachment objects with a shared key - Need a Domino Consultant? Call NotesMail +1 212-599-2048- HCLSoftware Business Partner

ADMINISTERING

Encrypting new attachment objects with a shared key
After you've created a shared key in a credential store to use to encrypt DAOS attachment objects, enable each server that uses the credential store to encrypt attachment objects with the key.

Before you begin

Complete the procedure Creating a shared key in the credential store.
Make sure that the design of the Domino directory has been refreshed with the pubnames.ntf template provided with Domino 12 or later.
Make sure that each server uses a credstore.nsf with the shared key.

About this task

After you follow this procedure:

Any new tier 1 attachment object created on the server is encrypted with the shared key. When attachment objects are in tier 1, each server has its own copy of the object. Tier 1 objects created prior to use of the shared key are encrypted with the shared key if they are pushed to tier 2 storage.
If you use tier 2 storage, once an attachment object encrypted with the shared key is in tier 2 storage, it resolves to a single object on servers that encrypt the objects with the shared key and that use the same S3 bucket.

Complete the following steps to configure each Domino server that uses a credential store with the shared key.

Procedure

1. Edit the Server document in the Domino directory and click the DAOS tab.

2. In the field DAOS object encryption, selectShared key.

3. A dialog box shows you the shared keys in the credstore.nsf on the server. Select the shared key to use and click OK.

4. Save the document.

5. Restart Domino:

restart server

6. Replicate the changes to other servers in the domain.

Help on Help

All Help Contents

Help on Help

All Help Contents