> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v3.0/configuration/setting-up-authentication/setting-up-integrated-windows-authentication.md).

# Setting up integrated windows authentication

The following guide will assist you in configuring your application to use Integrated Windows Authentication (IWA).

{% hint style="warning" %}
Note, that we recommend that you use a strong authentication mechanism such as OpenID Connect, where you have the ability to enforce multifactor authentication on users attempting to access your application. Access Manager fully supports modern OIDC providers such as [Microsoft Entra ID](/ams/v3.0/configuration/setting-up-authentication/setting-up-authentication-with-azure-ad.md) and [Okta](/ams/v3.0/configuration/setting-up-authentication/setting-up-authentication-with-okta.md).
{% endhint %}

## Part 1: Configure the SPN

To ensure kerberos authentication works correctly you'll need to register an SPN for the Access Manager service account.

The SPN must be in the format of `HTTP/{dnsName}` where `{dnsName}` is the external-facing DNS hostname used by the clients.

If this SPN is not set correctly, the following warning will appear in the `Service account` section of the `Host configuration` page. You can use the "Set SPN..." script to correct the problem. ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-1e1b476456c42778a09646841758b009ebffd969%2Fspn-warning.png?alt=media)

## Part 2: Configure Lithnet Access Manager

![!](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-1955613d81f641f5b577267e34044f671aed6442%2Fui-page-authentication-iwa.png?alt=media)

1. Open the Lithnet Access Manager Service Configuration Tool
2. Select the `App configuration\User authentication` page
3. Select `Integrated windows authentication` as the authentication provider
4. Select `Negotiate` for the authentication scheme.

{% hint style="danger" %}
The use of NTLM and basic auth is not recommended and are provided for testing purposes only.
{% endhint %}

To restrict clients to the use of Kerberos only, disable incoming NTLM authentication for the server using [group policy](https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-incoming-ntlm-traffic).


---

# 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.lithnet.io/ams/v3.0/configuration/setting-up-authentication/setting-up-integrated-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.