Power BI Connection Issue with Simba ODBC Driver and Kyuubi Authentication

[ratheeshkumar]

Hi Team,

I am using Power BI Desktop (Version: 2.138.1203.0, 64-bit) and the Simba ODBC driver (Version: 2.08.02.1013) to connect to the Spark Thrift Server. The Kyuubi gateway is configured to enable password authentication for the Thrift Server.

When I connect using Beeline, it prompts for credentials, and upon providing them, I am successfully connected to the terminal. However, when attempting the same connection from Power BI using the Simba ODBC driver, I encounter a credentials-related error. Interestingly, even when I intentionally input incorrect credentials, the error message on the Kyuubi server remains the same. I suspect that the Simba driver might be altering the password during the connection process. Any insights on this?

The connection string is - Driver={Simba Spark ODBC Driver};host=<Host Name>;port=10009

The error message I see in the kyuubi is 

- 2024-12-02 10:03:25.949 ERROR KyuubiTBinaryFrontendHandler-Pool: Thread-61 org.apache.kyuubi.shaded.thrift.transport.TSaslTransport: SASL negotiation failure
javax.security.sasl.SaslException: Error validating the login [Caused by javax.security.sasl.AuthenticationException: Password does not match or no such user. user: kyuubi, password: *********(length:9)]
at org.apache.kyuubi.service.authentication.PlainSASLServer.evaluateResponse(PlainSASLServer.scala:80)
at org.apache.kyuubi.shaded.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(TSaslTransport.java:507)
at org.apache.kyuubi.shaded.thrift.transport.TSaslTransport.open(TSaslTransport.java:250)
at org.apache.kyuubi.shaded.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:44)
at org.apache.kyuubi.shaded.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:199)
at org.apache.kyuubi.shaded.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:227)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Caused by: javax.security.sasl.AuthenticationException: Password does not match or no such user. user: kyuubi, password: *********(length:9)
at org.apache.kyuubi.service.authentication.JdbcAuthenticationProviderImpl.$anonfun$authenticate$4(JdbcAuthenticationProviderImpl.scala:87)
at org.apache.kyuubi.service.authentication.JdbcAuthenticationProviderImpl.$anonfun$authenticate$4$adapted(JdbcAuthenticationProviderImpl.scala:84)
at org.apache.kyuubi.util.JdbcUtils$.$anonfun$executeQuery$3(JdbcUtils.scala:81)
at org.apache.kyuubi.util.JdbcUtils$.withCloseable(JdbcUtils.scala:43)
at org.apache.kyuubi.util.JdbcUtils$.$anonfun$executeQuery$2(JdbcUtils.scala:80)
at org.apache.kyuubi.util.JdbcUtils$.withCloseable(JdbcUtils.scala:43)
at org.apache.kyuubi.util.JdbcUtils$.$anonfun$executeQuery$1(JdbcUtils.scala:78)
at org.apache.kyuubi.util.JdbcUtils$.withCloseable(JdbcUtils.scala:43)
at org.apache.kyuubi.util.JdbcUtils$.withConnection(JdbcUtils.scala:50)
at org.apache.kyuubi.util.JdbcUtils$.executeQuery(JdbcUtils.scala:77)
at org.apache.kyuubi.service.authentication.JdbcAuthenticationProviderImpl.authenticate(JdbcAuthenticationProviderImpl.scala:84)
at org.apache.kyuubi.service.authentication.PlainSASLHelper$PlainServerCallbackHandler.handle(PlainSASLHelper.scala:68)
at org.apache.kyuubi.service.authentication.PlainSASLServer.evaluateResponse(PlainSASLServer.scala:74)
... 8 more

[ratheeshkumar]

Thank you for your response, Tom Shen.

We are using basic username and password authentication in Kyuubi (JDBC). I am unsure if this is also considered SASL and do not have much insight into SASL-related configurations for both Kyuubi and Simba.

I reviewed the Kyuubi logs, and they only indicate messages about incorrect credentials. I am not sure how to access or review the Simba logs, but I will look into this.

On a positive note, the connection works with the Spark connector from Power BI. However, I believe the developer community prefers using ODBC.

[v-xingshen-msft]

Hi @ratheeshkumar ,

It's been a while since I've heard back from you and I wanted to follow up. After you went to the developer community and posted, did the developer community provide you with a solution, and if the issue has been resolved or moved to the developer community, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

[v-xingshen-msft]

Hi @ratheeshkumar ,
Based on your error message, it appears that SASL authentication failed and password or username authentication was not passed. The error message returned by the Kyuubi server remains unchanged even if incorrect credentials are entered.
This may be due to the following reasons:
1. SASL Configuration Problems: The SASL protocol between the Simba ODBC Driver and Kyuubi may not be properly negotiated or configured.
2. Driver version compatibility: Compatibility issues between the Simba ODBC Driver version and the Kyuubi version.
3. As you mentioned the Simba ODBC Driver may have changed passwords or performed other incorrect processing during the transfer.
Here are some suggestions for you:
1. You can check the logs of both Simba and Kyuubi: By checking the logs, you can learn more about the root cause of the authentication failure. Typically, Kyuubi will provide more details about the authentication failure, from which you can figure out if it was a password, username, or other authentication configuration problem.
2. If you are using the Simba Spark ODBC driver to connect to Kyuubi, make sure that the Simba version is compatible with the Kyuubi version. Some Kyuubi versions (e.g. 1.5.x) may have compatibility issues with older Simba drivers.
[Bug] Connect from PowerBI · Issue #3032 · apache/kyuubi · GitHub
If the above suggestions do not fully resolve your problem, you should contact Simba Technical Support or Kyuubi Technical Support and provide them with detailed error logs and configuration information so that they can help you diagnose and resolve the problem.

Hope it helps!

Best regards,
Community Support Team_ Tom Shen

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.