Server Policies – Shared Secrets

In the Shared Secrets tab of the server policies, you can configure global settings related to sharing entries, which will then apply to the entire server by default.

The actual process of sharing is conducted via the client. If settings are defined in these policies, users are required to comply with them. For example, if two-factor authentication is required, this cannot be disabled when sharing a secret on the client.

Supported Protocols

Here you can specify whether you want to allow entries to be shared only within the server (PD-SERVER). This means that entries can only be shared with users who also have a Password Depot client (and, for example, do not have basic authorization for a database in which the entry is located).

If you enable the HTTPS option, you allow entries to be shared via a web browser. This allows users who are not implemented in the Password Depot infrastructure (e.g., customers) to be granted access to entries. Anyone with the link can access the secret via a web browser.

Approval

You can specify which approval is required to access a shared entry. You can set whether a supervisor must give their approval (N-of-M). In addition, a minimum number of required approvals (N) can be specified if the first option is active. Values from 1 to 7 can be set here.

Access Control

You can also set certain restrictions within the scope of access control. This includes a maximum open limit (number of times that the corresponding entry may be opened, you can set a value from 1 to 1,000). You can also set a maximum lifetime of a shared secret (in hours; values from 1 to 64,384 can be set). In addition, you have the option of requiring two-factor authentication.

NOTE: Two-factor authentication can only be required for sharing entries via the PD-SERVER protocol.

NOTE: Find more information on Shared Secrets here.

NOTE: By clicking Restore default settings, you can reset the settings in the Shared Secrets tab back to their defaults and thus discard any changes.