$customHeader
Skip to end of banner
Go to start of banner

Secrets Management

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Overview

Secrets Management enables organizations to use a third-party secrets manager to store endpoint credentials. Instead of entering credentials directly in SnapLogic Accounts and relying on SnapLogic to encrypt them, the Accounts contain only the information necessary to retrieve the secrets. During validation and execution, Pipelines obtain the credentials directly from the secrets manager. With Secrets Management, the configured secrets are never stored by the SnapLogic control plane or by Snaplex nodes.

Only organizations using self-managed Snaplexes (Groundplexes) can subscribe to Secrets Management. Currently, we support the HashiCorp Vault secrets manager. You can use the Cloud, Enterprise, or Open Source edition of Vault.

Limitations

The following limitations apply:

  • Secrets Management is available only for self-managed Snaplexes (Groundplexes).

  • Secrets Management works only for Account credentials, not for SnapLogic authentication or node server keys.

  • Only dynamic Account types support Secrets Management.

Workflow

The high-level procedures required to use Secrets Management include:

  1. Obtain a subscription for Secrets Management by contacting your SnapLogic CSM.

  2. An administrator of the secrets manager configures the storage for endpoint credentials, creates authentication roles and access permissions, and generates secrets.

  3. The administrator of Snaplex nodes configures them with the token and the information required to communicate with the secrets manager.

  4. In SnapLogic, a Pipeline designer or Org admin configures the dynamic accounts to authenticate with the secrets manager.

Related Content

  • No labels