Error connecting to SQL Server Database while using Windows Integrated Security
search cancel

Error connecting to SQL Server Database while using Windows Integrated Security

book

Article ID: 268514

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

We are trying to connect to Microsoft SQL Server, which we connect generally through the current and other instances on a daily basis. We have run the masking job in 348 for the first time since the change of port number.  We have used FDM UI and CMD to run this and got the error below:

Error during opening connection: null
java.security.PrivilegedActionException: com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication. ClientConnectionId:4b1b07ee-0e2e-4bd1-894a-64acb81dfdde
        at java.security.AccessController.doPrivileged(Native Method)

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication. ClientConnectionId:4b1b07ee-0e2e-4bd1-894a-64acb81dfdde

Caused by: java.lang.UnsatisfiedLinkError: Unable to load authentication DLL mssql-jdbc_auth-12.2.0.x64
        at com.microsoft.sqlserver.jdbc.AuthenticationJNI.<clinit>(AuthenticationJNI.java:63)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:5012)
        ... 21 more

Environment

Release : FDM 4.10

Cause

The system where FDM is installed is unable to locate and load the dll used to connect to SQL Server when using Windows Integrated Security

Resolution

Connect to Microsoft SQL Server Using Windows Authentication in Fast Data Masker

Symptom: The data that I want to mask is available in a Microsoft SQL Server database that allows only Windows (Integrated authentication. How can I connect to this database from Fast Data Masker so that I can mask the required data?

Solution: You might need to mask the data that resides in a Microsoft SQL Server database that has been configured only for Windows authentication, not for the Microsoft SQL Server authentication. In such cases, follow these steps to establish the connection:
  1. Close the Fast Data Masker application.
  2. Navigate to the SQLSERVER_DLLs folder under the FastDataMasker installation folder (by default, C:\Program Files\Grid-Tools\FastDataMasker).
  3. Copy the file named mssql-jdbc_auth-12.2.0.x64.dll from the x64 subfolder. This is the 64-bit version of the DLL and is the one you need, assuming your system runs on a 64-bit processor.
  4. Place the mssql-jdbc_auth-12.2.0.x64.dll file into the FastDataMasker folder (by default, C:\Program Files\Grid-Tools\FastDataMasker).
  5. Launch the Fast Data Masker UI.
  6. Enter the Microsoft SQL Server database connection details.
  7. Make sure the username and password fields are left blank.
  8. Save the information.
  9. Click the Connect button.
 
You can now connect to the Microsoft SQL Server database that allows connections using only Windows authentication.
 
Note: After copying the mssql-jdbc_auth-12.2.0.x64.dll file, if you get the error message like This driver is not configured for windows authentication, it is most likely that the incorrect version of mssql-jdbc_auth-12.2.0 dll file has been copied. Repeat the process with a different version of the DLL.
 
In some cases, the system is still unable to locate the mssql-jdbc_auth-12.2.0.x64.dll. If this is the case, modify the Windows PATH Environment Variable, and add the FastDataMasker installation directory (C:\Program Files\Grid-Tools\FastDataMasker) to the PATH variable, and save the changes. Relaunch the FDM UI and test the connection.

Additional Information

With the release of TDM 4.10, we now support another option for Integrated Security using the NTLM option. For more information regarding using NTLM, please see https://techdocs.broadcom.com/us/en/ca-enterprise-software/devops/test-data-management/4-10/provisioning-test-data/defining-test-data/defining-test-data-using-the-ca-tdm-portal/create-and-edit-connection-profiles.html