Open topic with navigation

# SecureData Encryption

To enable SecureData encryption, you must provide the SecureData server details in the Deployment Template for a connector.

Note: CTHs cannot be configured with SecureData encryption.

If any proxy settings are required, these must also be provided in the Deployment Template.

To explicitly specify that no proxy be used for the SecureData client, no parameters are needed in the Deployment Template. In addition, edit the file `/etc/profile.d/proxy.sh` (or its equivalent on Windows VM) and add/edit the line “export no_proxy and export NO_PROXY” with your SecureData server details.

If your SecureData client needs a certificate, then upload the valid certificate to ArcMC's cacerts repository when creating the deployment template.

After all settings are configured, and a connection is ensured from the connector host to the SecureData server, you can deploy the connector using the Instant Connector Deployment process.

Warning: SecureData settings may only be updated once. Once encryption is turned on, it may not be turned off. Make sure you wish to use encryption before activating it.