[
https://issues.apache.org/jira/browse/IGNITE-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501773#comment-16501773
]
Vladimir Ozerov commented on IGNITE-8701:
-----------------------------------------
[~ilyak], reopening, this is an issue. The problem is that we do not check
authentication enabled flag in JDBC driver. The same logic implemented
correctly for ODBC and thin clients.
> 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
> 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)
