Microsoft SQL Server
Learn how to automatically rotate Microsoft SQL Server user passwords.
The Infisical SQL Server secret rotation allows you to automatically rotate your database users’ passwords at a predefined interval.
Prerequisites
- Create two SQL Server logins and database users with the required permissions. We’ll refer to them as
user-a
anduser-b
. - Create another SQL Server login with permissions to alter logins for
user-a
anduser-b
. We’ll refer to this as theadmin
login.
Here’s how to set up the prerequisites:
To learn more about SQL Server’s permission system, please visit this documentation.
How it works
- Infisical connects to your database using the provided
admin
login credentials. - A random value is generated and the password for
user-a
is updated with the new value. - The new password is then tested by logging into the database.
- If test is successful, it’s saved to the output secret mappings so that rest of the system gets the newly rotated value(s).
- The process is then repeated for
user-b
on the next rotation. - The cycle repeats until secret rotation is deleted/stopped.
Rotation Configuration
Open Secret Rotation Page
Head over to Secret Rotation configuration page of your project by clicking on Secret Rotation
in the left side bar
Click on Microsoft SQL Server card
Provide the inputs
SQL Server admin username
SQL Server admin password
SQL Server host url (e.g., your-server.database.windows.net)
Database port number (default: 1433)
Database name (default: master)
The first login name to rotate - user-a
The second login name to rotate - user-b
Optional database certificate to connect with database
Configure the output secret mapping
When a secret rotation is successful, the updated values needs to be saved to an existing key(s) in your project.
The environment where the rotated credentials should be mapped to.
The secret path where the rotated credentials should be mapped to.
What interval should the credentials be rotated in days.
Select an existing secret key where the rotated database username value should be saved to.
Select an existing select key where the rotated database password value should be saved to.
FAQ
Why can't we delete the other user when rotating?
Why can't we delete the other user when rotating?
When a system has multiple nodes by horizontal scaling, redeployment doesn’t happen instantly.
This means that when the secrets are rotated, and the redeployment is triggered, the existing system will still be using the old credentials until the change rolls out.
To avoid causing failure for them, the old credentials are not removed. Instead, in the next rotation, the previous user’s credentials are updated.
Why do you need an admin account?
Why do you need an admin account?
The admin account is used by Infisical to update the credentials for user-a
and user-b
.
You don’t need to grant all permissions for your admin account but rather just the permission to alter logins (ALTER ANY LOGIN).
How does this work with Azure SQL Database?
How does this work with Azure SQL Database?
When using Azure SQL Database, you’ll need to:
- Use the full server name as your host (e.g., your-server.database.windows.net)
- Ensure your admin account is either the Azure SQL Server admin or an Azure AD account with appropriate permissions
- Configure your Azure SQL Server firewall rules to allow connections from Infisical’s IP addresses