Feedback
Did this article resolve your question/issue?

   

Article

Can't connect to SQL Server using Windows Authentication after upgrading to 6.0

Information

 
TitleCan't connect to SQL Server using Windows Authentication after upgrading to 6.0
URL NameCan-t-connect-to-SQL-Server-using-Windows-Authentication-after-upgrading-to-6-0
Article Number000154368
EnvironmentProduct: Progress DataDirect for JDBC for SQL Server driver
Version: 6.0
OS: Java
Database: SQL Server
Application: All supported applications
Question/Problem Description
Can't connect to SQL Server using Windows Authentication after upgrading to Progress DataDirect for JDBC for SQL Server 6.0 driver
 
Steps to Reproduce
Clarifying Information
Setting the connection parameter AuthenticationMethod=auto.
Connection defaulting to Kerberos.
Same connection parameters with driver version 5.1 connect without error.
 
Error MessageKerberos Authentication is not supported by this SQLServer. The driver attempted Kerberos authentication because the AuthenticationMethod connect option was "auto" and no username/password was specified.
Defect Number
Enhancement Number
Cause
A driver change was made to removed NTLM from the driver's AUTO functionality in the 6.0 release because Microsoft points out that using NTLM is a security risk.
For additional information reference Microsoft's JDBC driver documentation
Resolution
The driver is behaving as expected.

 
Workaround
Set AuthenticationMethod = ntlm to connect.
Notes
Last Modified Date4/6/2020 1:54 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.