Setting up integrated windows authentication
Last updated
Was this helpful?
Last updated
Was this helpful?
The following guide will assist you in configuring your application to use Integrated Windows Authentication (IWA).
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 and .
Lithnet Access Manager uses kernel-mode authentication, which means the computer account, rather than the service account is used to authenticate the client. This means that the Kerberos service principal name must be applied to the computer account, rather than the service account.
If your web URL hostname is different to your machines AD hostname, then you'll need to register an SPN for this hostname.
Run the following command to set the SPN. Replace {dnsName} with the hostname web clients will use to access the service and {computerNetBIOSName} with the AD computer name
For a website called accessmanager.lithnet.local running on computer AMSWEB01, the command would be
Open the Lithnet Access Manager Service Configuration Tool
Select the App configuration\User authentication page
Select Integrated windows authentication as the authentication provider
Select Negotiate for the authentication scheme.
The use of NTLM and basic auth is not recommended and are provided for testing purposes only.
To restrict clients to the use of Kerberos only, disable incoming NTLM authentication for the server using .
