Delinea Secret Server
Read scan credentials from Delinea Secret Server with an OAuth2 sign-in and the secret field endpoint, using the delinea provider type in the runner's provider file.
Delinea Secret Server
The delinea provider reads one field of a secret from Delinea Secret Server (or Delinea Platform) through its REST API. The runner signs in with OAuth2, then reads the field. Safeguard works with Secret Server through this public API.
Reference
pam://delinea/<secretId>/<fieldSlug>[#password|#username]<secretId>is the secret's numeric id, shown in Secret Server.<fieldSlug>is the field of the secret's template, for examplepassword,usernameorprivate-key. Letters, digits, dash and underscore.#usernamereads theusernamefield.#passwordor nothing reads the field you named.
Example: pam://delinea/4711/password. As in other providers, a reference can name the configured provider instead of its type: pam://ss-prod/4711/password.
Settings
| Setting | Meaning |
|---|---|
url | The Secret Server address including its application path, for example https://secretserver.example.internal/SecretServer. |
auth | password (default): the OAuth2 password grant with api_user and api_key. client-credentials: the client credentials grant, with api_user as the client id and api_key as the client secret. |
api_user | The application account, or the client id. |
api_key | Its password, or the client secret. env://NAME or file:///path, never inline. |
token_path | The sign-in path. Default /oauth2/token. |
fetch_path | The read path. Default /api/v1/secrets/{{id}}/fields/{{slug}}. |
token_ttl | How long a token is reused. |
The settings every provider takes (timeout, ca_cert, client_cert, client_key, retries, allowed_refs, allow_http) apply as well. See Runner configuration.
providers:
- name: ss-prod
type: delinea
url: https://secretserver.example.internal/SecretServer
auth: password
api_user: svc-safeguard
api_key: file:///etc/safeguard/delinea-password
ca_cert: /etc/safeguard/internal-root-ca.pem
allowed_refs:
- "4711/*"
- "4712/*"In your Secret Server
Create an application account for Safeguard and give it read access to the secrets your scans use, and nothing else. The secrets it reads must not need check-out, a comment or approval: Safeguard does not drive those workflows, and a secret that needs one answers FORBIDDEN with Secret Server's message. If a secret needs a comment, use the REST connector with the restricted field endpoint.
Test
safeguard secrets test pam://delinea/4711/passwordIn the app, register the provider on the Providers tab. The form for Delinea Secret Server is generated from the settings above.
BeyondTrust Password Safe
Read scan credentials from BeyondTrust Password Safe through its public API, with a password request per scan that is checked in when the scan ends.
Azure Key Vault and AWS Secrets Manager
Read scan credentials from Azure Key Vault or AWS Secrets Manager with the runner's own cloud identity.