In the ODBC admin when you configure a DSN you will see a SSL Options button in the Authentication section. Once you click it, you will see a window with a list of options, make sure to uncheck Enable SSL.
For more info on the ODBC driver see https://maprdocs.mapr.com/home/attachments/JDBC_ODBC_drivers/DrillODBCInstallandConfigurationGuide.pdf --Andries On 5/10/18, 8:06 AM, "Peter Edike" <peter.ed...@interswitchgroup.com> wrote: How to disable ssl on driver -----Original Message----- From: Andries Engelbrecht <aengelbre...@mapr.com> Sent: Thursday, May 10, 2018 4:03 PM To: user@drill.apache.org Subject: Re: Handhsake Error My apologies after a bit more digging, I seem to found the issue in my environment. My ODBC driver kept enabling SSL for the connection causing the handshake error. I had to verify and turn SSL off manually. Verify that SSL is disabled on your ODBC driver connection or the DSN. Then for Tableau to work properly I had to turn of both authentication as well as impersonation. See setting in drill-override.conf drill.exec: { security.user.auth.enabled: false, impersonation.enabled: false, security.user.encryption.sasl.enabled: false, security.user.encryption.ssl.enabled: false } This obviously is not very secure, but works in my environment. Drill 1.12 with ODBC 1.3.16. --Andries On 5/10/18, 7:54 AM, "Andries Engelbrecht" <aengelbre...@mapr.com> wrote: Interesting, I did a quick test and it seems to be an issue with Authentication disabled on the drillbit. In my drill-override.conf I turn off authentication and impersonation drill.exec: { security.user.auth.enabled: false, impersonation.enabled: false, security.user.encryption.sasl.enabled: false, security.user.encryption.ssl.enabled: false } FYI, you may also want to make sure SSL it not enabled. When I restart the drillbit and try to connect with the ODBC driver I get the following error [MapR][Drill] (30) Handshake failure occurred while trying to connect to local=ip-172-31-47-166:31010. Server message: handshake: short read And in the drillbit.log I see 2018-05-10 14:45:30,553 [UserServer-1] ERROR o.a.d.exec.rpc.RpcExceptionHandler - Exception in RPC communication. Connection: /172.31.47.166:31010 <--> /172.31.7.24:49715 (user server). Closing connection. This looks like a bug, and related to similar user issues on this list. Perhaps someone else can verify as well and log a bug. I noticed other issues when connecting via Tableau with the metadata queries failing as well as it was expecting a username to use. Very unfortunate error as the channel gets closed leading to a handshake error for the user on an user authentication issue. As a workaround I would suggest you enable at least PLAIN authentication on the drillbit and use user/pass to access. --Andries On 5/10/18, 7:18 AM, "Peter Edike" <peter.ed...@interswitchgroup.com> wrote: That’s the exact location from which I downloaded the odbc driver. There is no authentication and yes drillbit is listening on 31010. I am connecting to drillbit directly Best regards, Peter Edike -----Original Message----- From: Andries Engelbrecht <aengelbre...@mapr.com> Sent: Thursday, May 10, 2018 3:08 PM To: user@drill.apache.org Subject: Re: Handhsake Error Make sure to use v 1.3.16 of the ODBC driver http://package.mapr.com/tools/MapR-ODBC/MapR_Drill/MapRDrill_odbc_v1.3.16.1049/ What authentication mechanism are you using? Also are you connecting to Drillbit directly or through Zookeeper? Try to connect to drillbit directly on port 31010 (if the drillbit config is the default ports), before trying zookeeper connections. --Andries On 5/10/18, 4:52 AM, "Peter Edike" <peter.ed...@interswitchgroup.com> wrote: The error I am getting occurs whilst I am trying to configure a DSN in the ODBC Admin. I am unable to do a connection test successfully; The version of ODBC Driver I am using is : MapR_Drill 1.3 My version of Drill is also: 1.12 Kind Regards -----Original Message----- From: Andries Engelbrecht <aengelbre...@mapr.com> Sent: Wednesday, May 9, 2018 9:09 PM To: user@drill.apache.org Subject: Re: Handhsake Error You stated you can connect with Drill Explorer on the client system, can you also configure a DSN in the ODBC admin and do a connection test successfully? You mentioned you used the No Authentication option to connect to Drill? What version of the ODBC driver are you using? Also which version of Drill? I assume you are running Windows? On Tableau are you using the Generic ODBC data source or the Apache Drill data source to connect to Drill? Try both and see if either works. The Apache Drill data source connection can only support No and Basic (user/pass authentication). --Andries On 5/9/18, 11:12 AM, "Peter Edike" <peter.ed...@interswitchgroup.com> wrote: I have increased the timeout and I am quite sure there are no authentication modules enabled. Is there anyway I can check if the request is getting to the server in the first place???? On May 9, 2018 7:09 PM, Parth Chandra <par...@apache.org> wrote: If you haven't tried it already, try increasing the handshake timeout. Do you have any security/authentication settings turned on? One possibility is that an authentication module is being accessed by the server during the handshake and the server is taking too long to reply to the handshake causing the timeout. On Wed, May 9, 2018 at 3:05 AM, Peter Edike < peter.ed...@interswitchgroup.com> wrote: > > Hello everyone > > I am trying to setup a datasource to connect to a drillbit running on a > host > I am using the Direct To DrillBit Option And have specified the > ip-address of the server on which the drill bit service is running as well > as the appropriate ports > I can telnet from my windows pc into this port via the telnet command but > all attempts to initiate a connection from DSN Setup Dialog Box Fails with > Handshake Error. > > FAILED! > > [MapR][Drill] (1010) Error occurred while trying to connect: [MapR][Drill] > (40) Handshake timed out (HandshakeTimeout=5) while trying to connect to > local=172.x.x.x:31010. Check whether Drillbit is running in a healthy state > or increase the timeout. > > Warm Regards > Peter E > ________________________________ > > This message has been marked as CONFIDENTIAL on Wednesday, May 9, 2018 @ > 11:05:23 AM > >
