Deprecation of Windows Authentication for Microsoft SQL Server resources
As part of our continued efforts to keep Retool secure and reduce vulnerabilities, hardened images become the default for self-hosted images starting in Q2 2027. As a result, Retool is deprecating Windows Authentication for Microsoft SQL Server resources. This deprecation also applies to Kerberos authentication for Microsoft SQL Server, which relies on Windows Authentication.
Hardened images are intentionally minimal and don't include the additional third-party libraries and utilities that Windows Authentication relies on. Microsoft SQL Server resources with Connect using Windows Auth enabled will eventually stop working, so plan to migrate before your resources are affected.
Who is affected
This change only affects self-hosted organizations with Microsoft SQL Server resources that have Connect using Windows Auth enabled.
What to do
Update each affected Microsoft SQL Server resource to use Username and password authentication with a SQL Server login:
- Create a SQL Server login with the permissions your apps and workflows need.
- Open the resource from the Resources page.
- Disable Connect using Windows Auth.
- Enter the SQL Server login in Database username and Database password. Use configuration variables or Retool secrets to store the credentials.
- Click Test connection, then save your changes.