Active directory secrets engine (API)

This is the API documentation for the Vault AD secrets engine. For general information about the usage and operation of the AD secrets engine, please see the Vault Active Directory documentation.

This documentation assumes the AD secrets engine is enabled at the /ad path in Vault. Since it is possible to enable secrets engines at any location, please update your API calls accordingly.

Configuration

The config endpoint configures the LDAP connection and binding parameters, as well as the password rotation configuration.

Password parameters

• ttl (int: "") - The default password time-to-live in seconds. Once the ttl has passed, a password will be rotated the next time it's requested.
• max_ttl (int: "") - The maximum password time-to-live in seconds. No role will be allowed to set a custom ttl greater than the max_ttl.
• password_policy (string: "") - Name of the password policy to use to generate passwords from. Mutually exclusive with length and formatter.

Deprecated parameters:

• length (string, optional) - The desired password length. Defaults to 64. Minimum is 14. Mutually exclusive with password_policy.
• formatter (string, optional) - Text into which the base64 password should be inserted, formatted like so: mycustom{{PASSWORD}}. Mutually exclusive with password_policy.

The following statement is applicable when using length and/or formatter, but not password_policy:

To meet Microsoft's password complexity requirements, all passwords begin with "?@09AZ" unless a formatter is provided. The formatter is for organizations with different, custom password requirements. It allows an organization to supply text that fulfills those requirements. {{PASSWORD}} must appear exactly once and can be anywhere in the text.

Connection parameters

• url (string, optional) - The LDAP server to connect to. Examples: ldaps://ldap.myorg.com, ldaps://ldap.myorg.com:636. This can also be a comma-delineated list of URLs, e.g. ldaps://ldap.myorg.com,ldaps://ldap.myorg.com:636, in which case the servers will be tried in-order if there are errors during the connection process. Default is ldap://127.0.0.1.
• connection_timeout (integer: 30 or string: "30s") - Timeout, in seconds, when attempting to connect to the LDAP server before trying the next URL in the configuration.
• request_timeout (integer: 90 or string: "90s") - Timeout, in seconds, for the connection when making requests against the server before returning back an error.
• starttls (bool, optional) - If true, issues a StartTLS command after establishing an unencrypted connection.
• insecure_tls - (bool, optional) - If true, skips LDAP server SSL certificate verification - insecure, use with caution!
• certificate - (string, optional) - CA certificate to use when verifying LDAP server certificate, must be x509 PEM encoded.

Binding parameters

• binddn (string, required) - Distinguished name of object to bind when performing user and group search. Example: cn=vault,ou=Users,dc=example,dc=com
• bindpass (string, required) - Password to use along with binddn when performing user search.
• userdn (string, optional) - Base DN under which to perform user search. Example: ou=Users,dc=example,dc=com
• upndomain (string, optional) - The domain (userPrincipalDomain) used to construct a UPN string for authentication. The constructed UPN will appear as [binddn]@UPNDomain. Example: if upndomain=example.com and binddn=admin, the UPN string admin@example.com will be used to login to Active Directory.

Other parameters

• last_rotation_tolerance (string, optional) - Tolerance duration to use when checking the last rotation time. Active Directory often shows a "pwdLastSet" time after Vault's because it takes a while for password updates to be propagated across a large cluster. By default, if Active Directory's last rotation time is within 5 seconds of Vault's, Vault considers itself to have been the last entity that rotated the password. However, if it's been more than 5 seconds, Vault thinks that something rotated the password out-of-band, and re-rotates it so it will "know" it and be able to continue returning it. This may be too low for larger Active Directory clusters, and too high for smaller ones.

Config management

At present, this endpoint does not confirm that the provided AD credentials are valid AD credentials with proper permissions.

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/ad/config

$ vault write ad/config \
    binddn="domain-admin" \
    bindpass="pa$$w0rd" \
    url="ldaps://127.0.0.1" \
    userdn="dc=example,dc=com"

Sample post payload

{
  "binddn": "domain-admin",
  "bindpass": "pa$$w0rd",
  "url": "ldaps://127.0.0.11",
  "userdn": "dc=example,dc=com"
}

Sample get response data

{
  "binddn": "domain-admin",
  "certificate": "",
  "insecure_tls": false,
  "length": 64,
  "max_ttl": 2764800,
  "starttls": false,
  "tls_max_version": "tls12",
  "tls_min_version": "tls12",
  "ttl": 2764800,
  "upndomain": "",
  "url": "ldaps://127.0.0.11",
  "userdn": "dc=example,dc=com"
}

Role management

The roles endpoint configures how Vault will manage the passwords for individual service accounts.

Parameters

• service_account_name (string, required) - The name of a pre-existing service account in Active Directory that maps to this role.
• ttl (string, optional) - The password time-to-live in seconds. Defaults to the configuration ttl if not provided.

When adding a role, Vault verifies its associated service account exists.

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/ad/roles/my-application

$ vault write ad/roles/my-application \
    service_account_name="my-application@example.com" \
    ttl=100

Sample post payload

{
  "service_account_name": "my-application@example.com",
  "ttl": 100
}

Sample get role response

{
  "last_vault_rotation": "2018-05-24T17:14:38.677370855Z",
  "password_last_set": "2018-05-24T17:14:38.6038495Z",
  "service_account_name": "my-application@example.com",
  "ttl": 100
}

Sample list roles response

Performing a LIST on the /ad/roles endpoint will list the names of all the roles Vault contains.

["my-application"]

Retrieving passwords

The creds endpoint offers the credential information for a given role.

Sample get request

$ curl \
    --header "X-Vault-Token: ..." \
    --request GET \
    http://127.0.0.1:8200/v1/ad/creds/my-application

$ vault read ad/creds/my-application

Sample get response

{
  "current_password": "?@09AZnh4Q5N4O5zdLk/4F8aIMgsnpDM6tSQEZCge3Mz1wXcZEgZhOa6OR748F96",
  "last_password": "?@09AZSen9TzUwK7ZhafS7B0GuWGraQjfWEna5SwnmF/tVaKFqjXhhGV/Z0v/pBJ",
  "username": "my-application"
}

Library management

The library endpoint configures the sets of service accounts that Vault will offer for check-out.

Parameters

• name (string: "", required): The name of the set of service accounts.
• service_account_names (string: "", or list: [] required): The names of all the service accounts that can be checked out from this set. These service accounts must only be used by Vault, and may only be in one set. These service accounts must already exist in Active Directory.
• ttl (duration: "24h", optional): The maximum amount of time a single check-out lasts before Vault automatically checks it back in. Defaults to 24 hours. Setting it to zero reflects an unlimited lending period. Uses duration format strings.
• max_ttl (duration: "24h", optional): The maximum amount of time a check-out last with renewal before Vault automatically checks it back in. Defaults to 24 hours. Setting it to zero reflects an unlimited lending period. Uses duration format strings.
• disable_check_in_enforcement (bool: false, optional): Disable enforcing that service accounts must be checked in by the entity or client token that checked them out. Defaults to false.

When adding a service account to the library, Vault verifies it already exists in Active Directory.

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/ad/library/accounting-team

Sample post payload

{
  "service_account_names": ["fizz@example.com", "buzz@example.com"],
  "ttl": "10h",
  "max_ttl": "20h",
  "disable_check_in_enforcement": false
}

Sample get response

{
  "service_account_names": ["fizz@example.com", "buzz@example.com"],
  "ttl": "10h",
  "max_ttl": "20h",
  "disable_check_in_enforcement": false
}

Sample list response

Performing a LIST on the /ad/library endpoint will list the names of all the sets of service accounts Vault contains.

["accounting-team"]

Check-out management

These endpoints help manage check-outs.

Check a credential out

Returns a 200 if a credential is available, and a 400 if no credential is available.

• name (string: "", required): The name of the set of service accounts.
• ttl (duration: "", optional): The maximum amount of time a check-out lasts before Vault automatically checks it back in. Setting it to zero reflects an unlimited lending period. Defaults to the set's ttl. If the requested ttl is higher than the set's, the set's will be used. Uses duration format strings.

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/ad/library/accounting-team/check-out

Sample post payload

{
  "ttl": "1h"
}

Sample post response

{
  "request_id": "364a17d4-e5ab-998b-ceee-b49929229e0c",
  "lease_id": "ad/library/accounting-team/check-out/aoBsaBEI4PK96VnukubvYDlZ",
  "renewable": true,
  "lease_duration": 36000,
  "data": {
    "password": "?@09QW0KZ8DSBu3deIu7XLY1NZqzwhozmMAZ6v0IcZJGOjs5GvpVMvOeW7/duls2",
    "service_account_name": "fizz@example.com"
  },
  "wrap_info": null,
  "warnings": null,
  "auth": null
}

Check a credential in

By default, check-in must be called by the same entity or client token used for check-out. To disable this behavior, use the disable_check_in_enforcement toggle on the library set. Or, use the ad/library/manage/:set_name/check-in behavior to force check-in of the account. Access to the "manage" endpoint should only be granted to highly privileged Vault users, like Vault operators.

If a caller attempts to check in a service account they're not authorized to check in, they will receive an error response. If they attempt to check in a service account they are authorized to check in, but it's already checked in, they will receive a successful response but the account will not be included in the check_ins listed. check_ins shows which service accounts were checked in by this particular call.

• name (string: "", required): The name of the set of service accounts.
• service_account_names (string: "", or list: [] optional): The names of all the service accounts to be checked in. May be omitted if only one is checked out.

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/ad/library/accounting-team/check-in

Sample post payload

{
  "service_account_names": ["fizz@example.com"]
}

Sample post response

{
  "request_id": "db45c714-3f68-b748-95bc-8f7467637a52",
  "lease_id": "",
  "renewable": false,
  "lease_duration": 0,
  "data": {
    "check_ins": ["fizz@example.com"]
  },
  "wrap_info": null,
  "warnings": null,
  "auth": null
}

Check the status of service accounts

Sample get request

$ curl \
    --header "X-Vault-Token: ..." \
    --request GET \
    http://127.0.0.1:8200/v1/ad/library/accounting-team/status

Sample get response

{
  "request_id": "9e44c8b5-d142-5867-2a11-49f3ba71215a",
  "lease_id": "",
  "renewable": false,
  "lease_duration": 0,
  "data": {
    "buzz@example.com": {
      "available": true
    },
    "fizz@example.com": {
      "available": false,
      "borrower_client_token": "4c653e473bf7e27c6759fccc3def20c44d776279",
      "borrower_entity_id": "631256b1-8523-9838-5501-d0a1e2cdad9c"
    }
  },
  "wrap_info": null,
  "warnings": null,
  "auth": null
}

Rotate root credentials

Rotate the bindpass to a new one known only to Vault.

Risks

1. When the bindpass is rotated, it successfully gets rotated in Active Directory but Vault can't store it so it becomes unknown.
2. If the binddn in use applies to more than one entity in Active Directory, root credential rotation will fail because it's unclear which entity to perform the operation for.

Mitigating risks

1. Always have another account that can provision a new binddn and bindpass to replace one whose password becomes unknown.
2. Ensure the binddn in use only applies to one entity by including all distinguished name parameters possible. For example, use "CN=vault-ad-test,CN=Users,DC=example,DC=com" instead of "CN=vault-ad-test".

Endpoints

Generally, rotate-root returns a 204. However, if rotate-root is already in progress, it may return a 200 with a warning that root credential rotation is already in progress.

Sample get request

$ curl \
    --header "X-Vault-Token: ..." \
    --request GET \
    http://127.0.0.1:8200/v1/ad/rotate-root

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    http://127.0.0.1:8200/v1/ad/rotate-root

Rotate role credentials

Manually rotate the password of a managed Active Directory service account.

Endpoints

Generally, rotate-role returns a 204. However, if rotate-role is already in progress, it may return a 200 with a warning that credential rotation is already in progress.

Sample post request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    http://127.0.0.1:8200/v1/ad/rotate-role/my-application