SQL Server Windows Authentication
This article outlines the external supporting files required to configure SQL Server Windows Authentication in OvalEdge. These files enable secure authentication using Windows domain credentials and support successful connector validation and connectivity to Microsoft SQL Server.
The required libraries vary based on the OvalEdge release version and JVM configuration (32-bit or 64-bit). When Windows Authentication is selected, OvalEdge uses additional JDBC driver files and native authentication libraries to establish connectivity through Windows-based authentication mechanisms.
OvalEdge Release7.2.x and later - Supporting Files
jtds-1.3.1.jar
1.3.1
Linux / Unix
Required JDBC driver library for Windows Authentication support. Place the file in the Third Party Jars directory.
sqljdbc_auth.dll
13.2.1.x86
32-bit JVM
Required authentication DLL for Windows Authentication (32-bit JVM). Place the file in the Tomcat bin directory.
sqljdbc_auth.dll
13.2.1.x64
64-bit JVM
Required authentication DLL for Windows Authentication (64-bit JVM). Place the file in the Tomcat bin directory.
ntlmauth.dll
-
Linux / Unix
Required native library for NTLM-based authentication. Place the file in the Tomcat bin directory.
OvalEdge Release6.3.x - Supporting Files
jtds-1.3.1.jar
1.3.1
Linux / Unix
Required JDBC driver library for Windows Authentication support. Place the file in the Third Party Jars directory.
ntlmauth.dll
-
Linux / Unix
Required native library for NTLM-based authentication. Place the file in the Tomcat bin directory.
sqljdbc_auth.dll
12.8.1.x86
32-bit JVM
Required authentication DLL for Windows Authentication (32-bit JVM). Place the file in the Tomcat bin directory.
sqljdbc_auth.dll
12.8.1.x64
64-bit JVM
Required authentication DLL for Windows Authentication (64-bit JVM). Place the file in the Tomcat bin directory.
For more information, refer to the Connector Drivers Setup Guide.
Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA
Last updated
Was this helpful?

