helm-external-secrets/docs/provider/senhasegura-dsm.md

senhasegura DevOps Secrets Management (DSM)

External Secrets Operator integrates with senhasegura DevOps Secrets Management (DSM) module to sync application secrets to secrets held on the Kubernetes cluster.

---

Authentication

Authentication in senhasegura uses DevOps Secrets Management (DSM) application authorization schema

You need to create an Kubernetes Secret with desired auth parameters, for example:

Instructions to setup authorizations and secrets in senhasegura DSM can be found at senhasegura docs for DSM and senhasegura YouTube channel

{% include 'senhasegura-dsm-secret.yaml' %}

---

Examples

To sync secrets between senhasegura and Kubernetes with External Secrets, we need to define an SecretStore or ClusterSecretStore resource with senhasegura provider, setting authentication in DSM module with Secret defined before

SecretStore

{% include 'senhasegura-dsm-secretstore.yaml' %}

ClusterSecretStore

{% include 'senhasegura-dsm-clustersecretstore.yaml' %}

---

Syncing secrets

In examples below, consider that three secrets (api-settings, db-settings and hsm-settings) are defined in senhasegura DSM

---

**Secret Identifier: ** api-settings

Secret data:

URL=https://example.com/api/example
TOKEN=example-token-value

---

**Secret Identifier: ** db-settings

Secret data:

DB_HOST='db.example'
DB_PORT='5432'
DB_USERNAME='example'
DB_PASSWORD='example'

---

**Secret Identifier: ** hsm-settings

Secret data:

HSM_ADDRESS='hsm.example'
HSM_PORT='9223'

---

Sync DSM secrets using Secret Identifiers

You can fetch all key/value pairs for a given secret identifier If you leave the remoteRef.property empty. This returns the json-encoded secret value for that path.

If you only need a specific key, you can select it using remoteRef.property as the key name.

In this method, you can overwrites data name in Kubernetes Secret object (e.g API_SETTINGS and API_SETTINGS_TOKEN)

{% include 'senhasegura-dsm-external-secret-single.yaml' %}

Kubernetes Secret will be create with follow .data.X

API_SETTINGS='[{"TOKEN":"example-token-value","URL":"https://example.com/api/example"}]'
API_SETTINGS_TOKEN='example-token-value'

---

Sync DSM secrets using Secret Identifiers with automatically name assignments

If your app requires multiples secrets, it is not required to create multiple ExternalSecret resources, you can aggregate secrets using a single ExternalSecret resource

In this method, every secret data in senhasegura creates an Kubernetes Secret .data.X field

{% include 'senhasegura-dsm-external-secret-multiple.yaml' %}

Kubernetes Secret will be create with follow .data.X

URL='https://example.com/api/example'
TOKEN='example-token-value'
DB_HOST='db.example'
DB_PORT='5432'
DB_USERNAME='example'
DB_PASSWORD='example'