ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8701) If Thin Client authentication is disabled on cluster, JDBC Thin Driver disallows supplying of login/password
Date Tue, 05 Jun 2018 13:36:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501781#comment-16501781
] 

ASF GitHub Bot commented on IGNITE-8701:
----------------------------------------

GitHub user devozerov opened a pull request:

    https://github.com/apache/ignite/pull/4137

    IGNITE-8701

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8701

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4137.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4137
    
----
commit 70ca50213f49be465bd38eca9ed972e17653b01a
Author: devozerov <vozerov@...>
Date:   2018-06-05T13:33:46Z

    Fixed.

----


> If Thin Client authentication is disabled on cluster, JDBC Thin Driver disallows supplying
of login/password
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8701
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8701
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.5
>            Reporter: Ilya Kasnacheev
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 2.6
>
>
> Previously, Ignite JDBC clients would just ignore supplied login and password.
> In 2.5, Ignite Thin JDBC driver will instead fail with following error:
> {code}
> The requested operation could not be performed due to the following error : Handshake
failed [driverProtocolVer=ClientListenerProtocolVersion [major=2, minor=5, maintenance=0],
remoteNodeProtocolVer=ClientListenerProtocolVersion [major=2, minor=5, maintenance=0], err=Handshake
error: Can not perform the operation because the authentication is not enabled for the cluster.]
> {code}
> when connecting to the cluster where authentication is disabled.
> This represents a *breaking change* in Apache Ignite API.
> Note that many tools (such as Informatica) insist on providing non-blank username and-or
password for JDBC connections. This will mean they *no longer work* with Apache Ignite with
no apparent workaround.
> My suggestion is to ignore login/password for JDBC Thin connections when authentication
is not enabled for cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message