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
Release : FDM 4.10
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
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