Configuring a TIBCO BusinessWorks database application running on Linux/Unix to connect to an SQL server using Windows Authentication.
Article ID: KB0092996
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
When an SQL server is running on a Windows machine with Windows Authentication with the TIBCO BusinessWorks database application running on a Linux/Unix environment, there is no direct way configure the TIBCO BusinessWorks application for Windows Authentication.
When an SQL server is running on a Windows machine with Windows Authentication with the TIBCO BusinessWorks database application running on a Linux/Unix environment, there is no direct way configure the TIBCO BusinessWorks application for Windows Authentication.
Issue/Introduction
Configuring a TIBCO BusinessWorks database application running on Linux/Unix to connect to an SQL server using Windows Authentication.
Resolution
Note that the following solution is based on the driver capability. There are no options available to control it from the BW product.
The JDBC driver does not support the integrated authentication when the driver runs on non-Windows operating systems. The driver also does not provide any functionality to supply Windows Authentication credentials, such as user name and password, when connecting to the SQL Server from a non-Windows operating systems. In such cases, the applications must use SQL Server Authentication. If you want to use Windows Authentication from a Linux environment, you may have to use 3rd party Kerberos authentication. Refer to the following two options.
If you are using DataDirect drivers, the "AuthenticationMethod" connection property controls which authentication mechanism the driver uses when establishing connections.
1. When AuthenticationMethod=kerberos, the driver uses Kerberos authentication when establishing a connection. The driver ignores any values specified by the User property and Password properties.
2. When AuthenticationMethod=ntlmjava, the driver uses NTLM when establishing a connection. Note that it requires that the User and Password properties be specified. If they are unspecified, the driver throws an exception. In addition, the driver requires the name of the domain server that administers the database server. You can specify it using the Domain property. If the Domain property is unspecified, the driver attempts to determine the domain server name from the User property. If no domain is specified, the driver throws an exception. This value is supported for Windows and UNIX/Linux clients.
Sample URL:
jdbc:tibcosoftwareinc:sqlserver://localhost:1433;databaseName=pubs;authenticationMethod=kerberos OR ntlmjava
Refer to the DataDirect driver's documentation. If you are using Microsoft drivers, review the following two links to obtain more information.
http://stackoverflow.com/questions/15844875/jdbc-intellij-failed-to-load-the-sqljdbc-auth-dll
https://blogs.msdn.microsoft.com/psssql/2015/01/09/jdbc-this-driver-is-not-configured-for-integrated-authentication/
Additional Information
http://stackoverflow.com/questions/15844875/jdbc-intellij-failed-to-load-the-sqljdbc-auth-dll
https://blogs.msdn.microsoft.com/psssql/2015/01/09/jdbc-this-driver-is-not-configured-for-integrated-authentication/
Refer to the following DataDirect driver document for more details.
Part 2: DataDirect Connect® Drivers: Microsoft SQL Server Driver > Authentication > Configuring NTLM Authentication
Part 2: DataDirect Connect® Drivers: Microsoft SQL Server Driver > Authentication > Configuring NTLM Authentication > Configuring the Driver: Specifying User Credentials
Feedback
Yes
No
Powered by
