[
https://issues.apache.org/jira/browse/IGNITE-13184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144835#comment-17144835
]
Ilya Kasnacheev commented on IGNITE-13184:
------------------------------------------
Also, when password is incorrect, we will report "Error: Authentication doesn't
support by remote server"
Wording is bad here, and the error seems imprecise: auth is in fact supported.
> ALTER USER SET PASSWORD is valid syntax but does not find user
> --------------------------------------------------------------
>
> Key: IGNITE-13184
> URL: https://issues.apache.org/jira/browse/IGNITE-13184
> Project: Ignite
> Issue Type: Bug
> Components: security, sql
> Affects Versions: 2.8.1
> Reporter: Ilya Kasnacheev
> Priority: Minor
>
> I have noticed the following:
> {code}
> 1: jdbc:ignite:thin://localhost> ALTER USER "ignite" set password 'abcdefg' ;
>
> Error: Failed to parse query. Пользователь "ignite" не найден
> User "ignite" not found; SQL statement:
> ALTER USER "ignite" set password 'abcdefg' [90032-197]
> (state=42000,code=1001)
> {code}
> The correct syntax is "WITH PASSWORD" but using "SET PASSWORD" does not
> cause parse error (like LIMIT PASSWORD or WHERE PASSWORD) would. It will
> report that user does not exist, which is false, and can probably throw an
> user off.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)