03-03-2016 08:13 AM
does anybody has an experience with a setup of MS SQL Linked server connecting to Impala via ODBC driver when Impala is configured to authenticate via LDAP?
The problem is that in the Linked Server config page under security tab there has to be defined a clear mapping from Local user (Users domain name in the SQL Server) vs Remote user name and password.
In the mapping when I enter the domain user name (abc\dwh) and map it to the same user and domain password, the mapping works, Impala recognize the user because validate the username and password against the Active Directory. Query runs without problem.
But what if I do not want to store here the dwh user's password (because after every change of the DWH user password I would have to change it here as well) and use Impersonation or even better the option of connecting under "login's current security context"?
This does not work, queries fail with this error:
OLE DB provider "MSDASQL" for linked server "Impala" returned message "[Cloudera][ImpalaODBC] (100) Error from the Impala Thrift API: SASL(-1): generic failure: All-whitespace username.".
Msg 7303, Level 16, State 1, Line 2
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "Impala".
The same error after this change.
So the conclusion is that MS SQL somehow does not send the users login and (hashed) password to the ODBC driver, and the driver just sends an empty user name (and password) to the Impala daemon.
Any suggestion how to resolve this issue?