• Supported versions
• Without the JTDS-SSO add-on
• With the JTDS-SSO add-on
• Setting up the JTDS-SSO add-on

Setting up NTLM access to Microsoft SQL Server via JTDS-SSO

This document describes how to access Microsoft SQL Server data sources in Windows authentication mode (with or without Single-Sign-On) from DigDash Enterprise.

Supported versions

• MS SQL Server 6.5
• MS SQL Server 7
• MS SQL Server 2000
• MS SQL Server 2005
• MS SQL Server 2008

Without the JTDS-SSO add-on

DigDash Enterprise natively supports access to Microsoft SQL Server without this add-on.

You can also access an MS SQL Server database in Windows authentication mode without this add-on by providing the domain, user login and password on the domain.

The following conditions must be met:

• In DigDash Enterprise Administrator the URL will look like this: jdbc:jtds:sqlserver://[HOST]/[DATABASE];domain=[DOMAIN]
• And the "User" and "Password" fields will be filled in (no need for the domain in the user name).

With the JTDS-SSO add-on

The JTDS-SSO add-on is only useful when you want to use Windows built-in authentication without specifying a user or password.

The following conditions must be met:

• The DigDash Enterprise server is installed on a Windows computer currently connected to an NT domain.
• The user account used to launch tomcat (or the service account) must have access to the database, or a different account and password must be specified when configuring a data source.

Setting up the JTDS-SSO add-on

In order to allow DigDash Enterprise to access an MS SQL Server database in Integrated Windows authentication mode you need to do the following:

1. Extract the folder <DigDash Enterprise installation directory>/add-ons/jtds-ss/jtds-sso.zip to a directory of your choice on the hard disk. This archive contains one ntlmauth.d ll per processor architecture folder.
2. Modify the System Path environment variable by adding the path to the folder containing the ntlmauth.dll corresponding to your processor architecture.

Note on using the jTDS + SSO connector with Kerberos In the Active Directory, the HTTP/<computername>.<domainename> url service must be mapped (declared "SPN") to the :