> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/additional-requirements/external-supporting-files-for-windows-authentication.md).

# External Supporting Files for Windows Authentication

This document outlines the external supporting files required to configure **Windows Authentication** in OvalEdge. These files are mandatory to enable secure authentication using **Windows domain credentials** and to ensure successful connector validation and connectivity.

The required libraries vary based on the **OvalEdge release version** and the **JVM architecture** (32-bit or 64-bit). When Windows Authentication is selected, OvalEdge relies on additional **JDBC driver files** and **native authentication libraries** to establish connectivity through Windows-based authentication mechanisms.

{% hint style="warning" %}
These supporting files are required **only when Windows Authentication is selected**.
{% endhint %}

### OvalEdge Release7.2.x - Supporting Files

<table><thead><tr><th width="166">File Name</th><th width="142">Version / Type</th><th width="180">Applicable JVM / OS</th><th width="466">Purpose</th></tr></thead><tbody><tr><td><code>jtds-1.3.1.jar</code></td><td>1.3.1</td><td>Linux / Unix</td><td>Required JDBC driver library for Windows Authentication support. Place the file in the Third Party Jars directory.</td></tr><tr><td><code>sqljdbc_auth.dll</code></td><td>13.2.1.x86</td><td>32-bit JVM</td><td>Required authentication DLL for Windows Authentication (32-bit JVM). Place the file in the Tomcat bin directory.</td></tr><tr><td><code>sqljdbc_auth.dll</code></td><td>13.2.1.x64</td><td>64-bit JVM</td><td>Required authentication DLL for Windows Authentication (64-bit JVM). Place the file in the Tomcat bin directory.</td></tr><tr><td><code>ntlmauth.dll</code></td><td>-</td><td>Linux / Unix</td><td>Required native library for NTLM-based authentication. Place the file in the Tomcat bin directory.</td></tr></tbody></table>

### OvalEdge Release6.3.x - Supporting Files

<table><thead><tr><th width="166">File Name</th><th width="142">Version / Type</th><th width="182">Applicable JVM / OS</th><th width="476">Purpose</th></tr></thead><tbody><tr><td><code>jtds-1.3.1.jar</code></td><td>1.3.1</td><td>Linux / Unix</td><td>Required JDBC driver library for Windows Authentication support. Place the file in the Third Party Jars directory.</td></tr><tr><td><code>ntlmauth.dll</code></td><td>-</td><td>Linux / Unix</td><td>Required native library for NTLM-based authentication. Place the file in the Tomcat bin directory.</td></tr><tr><td><code>sqljdbc_auth.dll</code></td><td>12.8.1.x86</td><td>32-bit JVM</td><td>Required authentication DLL for Windows Authentication (32-bit JVM). Place the file in the Tomcat bin directory.</td></tr><tr><td><code>sqljdbc_auth.dll</code></td><td>12.8.1.x64</td><td>64-bit JVM</td><td>Required authentication DLL for Windows Authentication (64-bit JVM). Place the file in the Tomcat bin directory.</td></tr></tbody></table>

***

&#x20;Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/connectors/additional-requirements/external-supporting-files-for-windows-authentication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.