This document describes how to use Windows Authentication to access SQL Server using a JDBC data source. The configuration with the jTDS and the Microsoft drivers will be explained.
Before creating a data source to a MS SQL Server database from Virtual DataPort using the jTDS driver and Windows Authentication follow these steps:
The option Pass-through session credentials can also be selected.
Troubleshooting note: In some cases adding the ntlmauth.dll library to the %SYSTEMROOT%/system32 folder will raise the error “SSO Failed: Native SSPI library not loaded” when creating the data source. If this happens, instead of adding the ntlmauth.dll file to the %SYSTEMROOT%/system32 folder copy it to the bin folder of the JRE used by the Denodo installation (<DENODO_HOME>/jre/bin if you are using the default JVM) and restart the VDP server afterwards.
To access MS SQL Server from VDP using the Microsoft driver and Windows Authentication:
When using the Microsoft Diver, the URI parameter IntegratedSecurity=true indicates that Windows credentials will be used by SQL Server to authenticate the user of the application.
If "true" the JDBC driver searches the local computer credential cache for credentials that have already been provided at the computer or network logon. If "false" the username and password must be supplied.
This means that the credentials used to authenticate to SQL Server will be the credentials used to log in the machine where the VDP Server is installed or the credentials used to run the VDP Server as a Windows Service.