Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Print Bookmark Alert me when this article is updated


ERROR: "[informatica][SQLServer JDBC Driver]Kerberos Authentication is not supported by this SQLServer./.../" while testing SQL server connection in EDC
Problem Description
When testing SQL server connection in Enterprise Data Catalog (EDC), the following error messages are displayed in the admin console:

The requested operation could not be performed due to the following error: 

[informatica][SQLServer JDBC Driver]Kerberos 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.

Informatica installation is on the Linux server. The user attempts to use Windows authentication to connect to SQL server. The Use trusted connection option is selected under connection properties.
Using a trusted connection in this scenario does not work.

NTLM authentication is not supported in Unix as per documentation:

Use trusted connection -> Enables the application service to use Windows authentication to access the database. The user name that starts the application service must be a valid Windows user with access to the database. By default, this option is cleared.
Windows and NTLM authentication is not certified for a Microsoft SQL Server 2017 version hosted on Linux.

Metadata Access Properties: Connection String -> UNIX supports NTLMv1 and NTLMv2 but not NTLM. If you connect with NTLM authentication, you can enable the Use trusted connection option in the MS SQL Server connection properties. If you connect with NTLMv1 or NTLMv2 authentication, you must provide the user name and password in the connection properties.

If AuthenticationMethod is set to ntlmjava, the driver uses NTLMv1 or NTLMv2 depending on the size of the NTLM password. NTLMv1 is used if the password is 14 bytes or less; NTLMv2 is used if the password is more than 14 bytes. A user ID and password must also be specified. This value is supported for Windows and UNIX/Linux clients.
Do as follows to resolve this issue:

From Admin console > Manage > Connections > your sql connection > Properties, disable Use trusted connection option.

Specify the username as windows_domain\username.
Append AuthenticationMethod=ntlmjava to the jdbc connection string.
Test connection from Admin console works fine after this.

For odbc connectivity, in the odbc.ini file in the server,  set the properties AuthenticationMethod=9, Domain=windows_domain, EnableQuotedIdentifiers=1​ in the DSN entry.
More Information
Applies To
Product: Enterprise Data Catalog; Data Quality
Problem Type: Configuration; Product Feature
User Type: Administrator
Project Phase: Configure
Product Version:
Database: Microsoft SQL Server
Operating System: Linux
Other Software:

Last Modified Date:7/1/2020 11:18 PMID:621308
People who viewed this also viewed


Did this KB document help you?

What can we do to improve this information (2000 or fewer characters)