The Azure databricks custom connector is throwing a SASL error when connecting via the web client (anywhere) or Analyst client (node manager only).

[David Boot-Olazabal]

The Azure databricks custom connector is throwing a SASL error when connecting via the web client (anywhere) or Analyst client (node manager only).

We can successfully create a working connection through the Analyst client on a developer's machine. But as soon as we try to run the created dashboard on the web client, it throws this error:

Spotfire.Dxp.Data.Exceptions.ImportException: Could not connect due to an unknown error.

External error:

ERROR [HY000] [TIBCO][ThriftExtension] (5) Error occurred while contacting server: invalid sasl status. This could be because you are trying to establish a non-SSL connection to a SSL-enabled server.

ERROR [HY000] [TIBCO][ThriftExtension] (5) Error occurred while contacting server: invalid sasl status. This could be because you are trying to establish a non-SSL connection to a SSL-enabled server.

What can we do to resolve this problem?

[David Boot-Olazabal]

The Azure databricks custom connector is probably hitting 'something' that prevents it to run properly in the web. Due to the limitations and timelines, we were unable to see what kind of walls we were hitting.

The work around that we used though, was to revert back to the native Databricks ODBC driver. With extra privileges for our SPN on the top level catalog (read permission) as well as setting our own catalog as the default, allowed us to bypass the problems we have seen with the Azure databricks custom connector. With the extra permissions in place, the web client is now also running smoothly against Databricks.