Specifies the method the driver uses to authenticate the user to the server when a connection is established. If the specified authentication method is not supported by the database server, the connection fails and the driver generates an error.
Valid Values
1 | 4 | 9 | 10 | 13
Behavior
If set to 1 (Encrypt Password), the driver sends the user ID in clear text and an encrypted password to the server for authentication.
If set to 4 (Kerberos Authentication), the driver uses Kerberos authentication. This method supports both Windows Active Directory Kerberos and MIT Kerberos environments. Setting this value to 4 also enables NTLMv2 and NTLMv1 authentication on Windows platforms. The protocol used for a connection is determined by the local security policy settings for the client.
(UNIX and Linux only) If set to 9 on Linux and UNIX platforms, the driver uses NTLMv1 or NTLMv2 authentication. The driver determines which protocol to use based on the size of the password provided. For passwords 14 bytes or less, the driver uses NTLMv1; otherwise, the driver uses NTLMv2. To connect to the database, users must supply the Windows User Id, Password, and, in some cases, Domain to the driver.
(UNIX and Linux only) If set to 10, the driver uses NTLMv2 authentication. To connect to the database, users must supply the Windows User Id, Password, and, in some cases, Domain to the driver.
If set to 13 (Active Directory Password), the driver uses Azure Active Directory (Azure AD) authentication when establishing a connection to an Azure SQL Database data store. All communications to the service are encrypted using SSL.
Important: Before enabling Azure AD authentication, see "Configuring Azure Active Directory Authentication" for requirements and additional information.
NTLM single sign on is supported only on Windows.