You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Sapego (JIRA)" <ji...@apache.org> on 2019/06/04 14:43:00 UTC
[jira] [Commented] (IGNITE-11875) Thin client is unable to
authenticate with long password
[ https://issues.apache.org/jira/browse/IGNITE-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855773#comment-16855773 ]
Igor Sapego commented on IGNITE-11875:
--------------------------------------
[~ptupitsyn] done. [~DmitriyGovorukhin] can you take a look on Java part please?
> Thin client is unable to authenticate with long password
> --------------------------------------------------------
>
> Key: IGNITE-11875
> URL: https://issues.apache.org/jira/browse/IGNITE-11875
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, odbc, thin client
> Affects Versions: 2.7
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Token authentication could use long usernames/passwords, that leads to "Invalid handshake message"
> ClientListenerNioServerBuffer:
> {code:java}
> if (cnt == msgSize) {
> byte[] data0 = data;
> reset();
> return data0;
> }
> else {
> if (checkHandshake && cnt > 0 && (msgSize > ClientListenerNioListener.MAX_HANDSHAKE_MSG_SIZE
> || data[0] != ClientListenerRequest.HANDSHAKE))
> throw new IgniteCheckedException("Invalid handshake message");
> return null;
> }
> {code}
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)