Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Configure Edge Encryption on the instance

Log in to subscribe to topics and get notified when content changes.

Configure Edge Encryption on the instance

Configure Edge Encryption by defining encryption keys, assigning fields and attachments to be encrypted, and specifying encryption patterns.

To configure Edge Encryption, you must be connected to the instance through the proxy. Test all changes on a sub-production instance before making the changes to the production instance.

Define encryption keys

After setting up one or more proxies, you must configure the instance to use the encryption keys. This means entering the key alias (name), the key's size (128 or 256), and key type (file, Keystore, or Safenet) on the instance. After configuring the encryption keys, the instance verifies that the keys are available to all proxies. You cannot make an encryption key the default key unless all proxies have the key.

Assign fields and attachments to be encrypted

Assigning fields and attachments to be encrypted means assigning an encryption type to the field or attachment. Before marking a field as encrypted, evaluate these issues.
  • Determine what system features might be impacted.
  • Examine all scripts for use of the field.
  • Make any desired adjustments to the field's size. After a field has been configured for encryption, the field size cannot be changed.

Marking a field to be encrypted expands the field size to hold the extra space needed to store the encrypted data. The process of expanding the field size can take a long time depending on the number of records in the table.

Specify encryption patterns

The encryption patterns are string patterns to be replaced by tokens before being sent to and stored in the instance. You can define a string pattern or use one of the predefined patterns.