Run kinit, passing in a principal name and password. You first need to configure Kerberos on the client and then ensure that the application can use the Kerberos credential of the default principal.Įnsure that you use kinit or PAM (Pluggable Authentication Module) to obtain and cache the TGT for the principal that the connection uses, via one of the following methods: Deploying a Linux or macOS ODBC Driver Application Designed to Run as a ServiceĪ system administrator can deploy an application to run as a service that uses Kerberos Authentication to connect to SQL Server.
ServerSPN and FailoverPartnerSPN are not supported. The -E option of sqlcmd and the -T option of bcp can also be used to specify integrated authentication see Connecting with sqlcmd and Connecting with bcp for more information.Įnsure that the client principal which is going to connect to SQL Server is already authenticated with the Kerberos KDC. When connecting with a DSN, you can also add Trusted_Connection=yes to the DSN entry in odbc.ini. For example: Driver='ODBC Driver 18 for SQL Server' Server=your_server Encrypt=yes Trusted_Connection=yes You can enable Kerberos integrated authentication by specifying Trusted_Connection=yes in the connection string of SQLDriverConnect or SQLConnect. Using Integrated Authentication to Connect to SQL Server from an ODBC Application See Using Azure Active Directory for more information.
It supports the MIT Kerberos Key Distribution Center (KDC), and works with Generic Security Services Application Program Interface (GSSAPI) and Kerberos v5 libraries.Īs of version 17.6, the driver also supports integrated authentication with Azure Active Directory using a federated account, system library limitations notwithstanding.
The Microsoft ODBC Driver for SQL Server on Linux and macOS supports connections that use Kerberos integrated authentication.
0 kommentar(er)
