Endpoint credentials

To enable SnapLogic apps require connection information and credentials to connect to your endpoints. The Designer and Classic Manager save these configurations as accounts. AutoSync saves them as credentials.

The SnapLogic Platform encrypts credentials and configuration data using an asymmetric key pair, which is unique for each environment (Org). When you enter sensitive properties in the browser, such as passwords, the platform encrypts them using the environment's public key. When you save, the platform passes the encrypted data over an HTTPS connection to the control plane. The control plane stores the encrypted information in a secure S3 bucket that uses server-side encryption for data at rest. When an executing pipeline needs to connect, the Snaplex retrieves credentials from the SnapLogic control plane. The Snaplex decrypts the data using the environment's private key but doesn't persist the credentials locally. At no time is data stored or transported over the wire in an unencrypted form.

For additional security:

  • Organizations using self-managed Snaplexes (Groundplexes) can subscribe to Enhanced Account Encryption or Secrets Management:
    • With Enhanced Account Encryption, your organization doesn't share the private key with SnapLogic but instead stores it on the Groundplex nodes. The control plane can not decrypt the account credentials.
    • With Secrets Management, your organization stores credentials in a third-party secrets manager. SnapLogic Accounts contain only the information necessary to access the secrets manager.
  • Organizations using Snaplexes managed by SnapLogic can configure secure connectivity to on-premises endpoints with Cloudplex Secure Connectivity.

SnapLogic standard encryption, Enhanced Encryption and Secrets Management do not protect against misuse by people in your organization. You should ensure that only authorized users have access to credentials.