Database Rotated Secret

You can create a Rotated Secret for a database user. Currently, Akeyless Rotated Secrets can be created for the following databases:

  • MySQL

  • MSSQL

  • Snowflake

  • PostgreSQL

  • Oracle

  • Cassandra

  • Redshift

  • MongoDB

Before you get started, ensure creating a Database Target that includes the hostname and connection settings, as well as credentials for a privileged user authorized to rotate credentials.

When a client requests a Rotated Secret value, the Akeyless Vault Platform connects to the database server through your Gateway to rotate the user password on your target database.

Create a Rotated Database Secret from the CLI

To create a Rotated Database Secret using the Akeyless CLI, run the following command:

akeyless create-rotated-secret --name <secret name> \
--gateway-url 'https:\\<Your-Akeyless-GW-URL:8000>' \
--target-name <target name to associate> \
--authentication-credentials <use-user-creds|use-target-creds> \
--rotator-type <password|target> \
--rotated-username <username> \
--rotated-password <password to rotate> \
--auto-rotate <true|false> \
--rotation-interval <1-365> \
--rotation-hour <hour in UTC>

Where:

  • name: A unique name of the Rotated Secret. The name can include the path to the virtual folder where you want to create the new Rotated Secret, using slash / separators. If the folder does not exist, it will be created together with the Rotated Secret.

  • gateway-url: Akeyless Gateway URL.

  • target-name: The name of the Database Target with which the Rotated Secret should be associated.

  • authentication-credentials: Determines how to connect to the target database.

    • use-user-creds - Use the credentials defined on the Rotated Secret item.
    • target-rotator-creds - Use the credentials defined on the Database Target item.

πŸ‘

Tip

Select target-rotator-creds if the Rotated Secret user is not authorized to change their own password, and a privileged user, like the Database Target user is required to change the password on behalf of the Rotated Secret user.

  • rotator-type: The type of credentials to be rotated. For Database Targets, choose:

    • password - to rotate the DB user password specified in the Rotated Secret
    • target - to rotate the password for the user specified in the Database Target.
  • rotated-username: The DB user whose password should be rotated.

  • rotated-password: The password to rotate.

  • auto-rotate: Enable auto-rotation if you need to update the password regularly. If this value is set to true, specify the rotation-interval in days, and optionally also the rotation-hour.

You can find the complete list of parameters for this command in the CLI Reference - Rotated Secrets section.

Create a Rotated Database Secret in the Akeyless Console

πŸ‘

Tip

To start working with Rotated Secrets from the Akeyless Console, you need to configure the Gateway URL thus enabling communication between the Akeyless SaaS and the Akeyless Gateway.

To create Rotated Secrets directly from the Akeyless Gateway, you can use the Gateway Configuration Manager.

  1. Log in to the Akeyless Console, and go to Secrets & Keys > New > Rotated Secret.

  2. Define a Name of the Rotated Secret, and specify the Location as a path to the virtual folder where you want to create the new Rotated Secret, using slash / separators. If the folder does not exist, it will be created together with the Rotated Secret.

  3. Define the remaining settings as follows:

  • Delete Protection: When enabled, protects the Rotated Secret from accidental deletion.

  • Target: Defines the name of the Database Target to be associated with the Rotated Secret.

  • Authenticate with the following credentials: Determines how to connect to the target database:

    • User credentials: Use the credentials defined inside the Rotated Secret item.
    • Target credentials: Use the credentials defined inside the Database Target item.

πŸ‘

Tip

Select Target credentials if the Rotated Secret user is not authorized to change their own password, and a privileged user, like the Database Target user, is required to change the password on behalf of the Rotated Secret user.

  • Rotator type: Determines the rotator type:

    • Password: Rotates the password defined inside the Rotated Secret item.
    • Target: Rotates the password defined inside the Database Target item.
  • Username: Defines the DB username which password should be rotated.

  • Password: Defines the password to rotate.

πŸ‘

Tip

You can rotate the password for the Database Target too, by creating a Rotated Secret with the Rotator type set to Target. When you're using a Target rotator, the access role with which this Rotated Secret is associated must have read and update permissions on the corresponding Target.

  • Gateway: Select the Gateway through which the secret will be rotated.

  • Protection Key: To enable Zero-Knowledge, select a key with a Customer Fragment. For more information about Zero-Knowledge, see Implement Zero Knowledge

  • Auto rotate: Determines if automatic rotation is enabled.

  • Rotation interval (in days): Defines the number of days (1-365) to wait between automatic password rotations when Auto Rotate is enabled.

  • Rotation hour (local time zone): Defines the time when the password should be rotated if Auto Rotate is enabled.

  1. Click Finish.

Did this page help you?