Last modified by jhurst on 2021/04/21 10:01
Show last authors
1 This document explains how to access Microsoft SQL Server data sources using Windows authentication (with or without Single-Sign-On) from DigDash Enterprise.
2
3 {{ddtoc/}}
4
5 = Supported versions =
6
7 * MS SQL Server 6.5
8 * MS SQL Server 7
9 * MS SQL Server 2000
10 * MS SQL Server 2005
11 * MS SQL Server 2008
12
13 = Without JTDS-SSO add-on =
14
15 DigDash Enterprise natively supports access to Microsoft SQL Server without using this add-on.
16
17 You can also access a MS SQL Server data base using Windows authentication without this add-on by specifying the domain name, the user login and password on this domain.
18
19 The following condition must be fulfilled:
20
21 * In DigDash Enterprise Administrator, the URL should look like this: jdbc:jtds:sqlserver:~/~/[HOST]/[DATABASE];domain=[DOMAIN]
22 * The « User » and « Password » fields should be specified (no need for the domain in the user field).
23
24 = With JTDS-SSO add-on =
25
26 The JTDS-SSO add-on is useful when you want to use the Windows integrated authentication without specifying a user name or password for the data base user.
27
28 The following conditions must be fulfilled:
29
30 * The DigDash Enterprise server is installed on a Windows computer currently connected to an NT domain
31 * The account used to launch tomcat (or the service account) must have access to the database, or you must specify a different account name and password when configuring the data source.
32
33 = Setting up the JTDS-SSO add-on =
34
35 To allow DigDash Enterprise to access a MS SQL Server data base with Windows authentication, you must do the following:
36
37 1. Extract the folder <DigDash Enterprise install folder>/add-ons/jtds-ss/**jtds-sso.zip** to a folder of your choice on the hard drive. This archive contains a DLL **ntlmauth.dll** for each processor architecture.
38 1. Modify the environnment System variable **Path** by adding the path to the folder containing the **ntlmauth.dll** __corresponding to your processor architecture__.
39
40 (% class="box infomessage" %)
41 (((
42 //__Note on using the jTDS-SSO connector with Kerberos__//
43 )))
44
45 In Active Directory, the service url HTTP/<computername>.<domainename> must be mapped (declared « SPN ») with the domain service account:
46
47 Setspn.exe -S HTTP/<computer-name>.<domaine-name>:<port> <domain-user-account>
48
49
50
51