Windows (AD) Authentication

Understanding AD integration

SSO happens between three entities in the same network domain:

After the initial contact with the user TempusServa validates the original AD authentication, and logs in the user if a matching username can be found. Optionally TempusServa can synchronize group memberships using regular LDAP querying.

Installing the SPNEGO servlet filter

Note the following guide is for Tomcat 6 or higher.

Installation part 1

The first part of the installation ensures the basic SSO communication is in place.

  1. Run pre flight checklist
  2. Run installation

Troubleshooting

After a succesfull test you should remove the jsp test file.

Installation part 2

The second part of the installation ensures TempusServa logs in the user based on the Windows authenticated username.

Install the SPNEGO filter on the TempusServa application

  1. Copy filter setting from the guide to <Tomcat>\webapps\<Application>\WEB-INF\web.xml
  2. Change the filter mapping from *.jsp to the login page
<filter-mapping>
    <filter-name>SpnegoHttpFilter</filter-name>
    <url-pattern>/login</url-pattern>
</filter-mapping>

Configure TempusServa to accept SSO by changing system configuration

ssoSpnegoAuthenticate = true

Finally restart Tomcat

Testing the setup

Find a suitable user

Login to a machine connected to the Domain controller

Navigate to the TempusServa login page and check if you are logged in and redirected to the main page.

Other results


Revision #1
Created 28 July 2025 09:26:58 by Theis Villumsen
Updated 28 July 2025 09:27:47 by Theis Villumsen