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

Taras Ledkov edited comment on IGNITE-8198 at 5/17/18 11:27 AM:
----------------------------------------------------------------

[~pgarg], thanks a lot.
My comments about user name case-sensitive-insensitive behavior.
I guess it cannot be called *case-insensitive*, but I have no idea for correct 
description it at the documentation.

1. JDBC doesn't support case-insensitive for username (AFAIK ODBC does't 
support too).
e.g.: {{jdbc:ignite:thin://192.168.0.50?user=test&password=test}}
User name {{test}} is user to authentication.

2. Not-qouted SQL identifier is transformed to *upper-case*. e.g.
{{CREATE USER test WITH PASSWORD 'test';}}
User {{TEST}} is created.
So, the URL {{jdbc:ignite:thin://192.168.0.50?user=test&password=test}} is 
processed with error *The user name or password is incorrect* because user 
{{test}} doesn't exist.




was (Author: tledkov-gridgain):
[~pgarg], thanks a lot.
My comments about user name case-sensitive-insensitive behavior.
I guess it cannot be called *case-insensitive*, but I have no idea for correct 
description it at the documentation.

1. JDBC doesn't support case-insensitive for username (AFAIK ODBC does't 
support too).
2. Not-qouted SQL identifier is transformed to *upper-case*. e.g.
{{CREATE USER test WITH PASSWORD 'test';}}
User {{TEST}} is created.


> Document how to use username/password for REST, drivers and thin clients
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-8198
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8198
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.5
>            Reporter: Prachi Garg
>            Assignee: Denis Magda
>            Priority: Major
>             Fix For: 2.5
>
>
> Overall, we have to update the following protocols/driving explaining how to 
> open a secured connection:
>  * JDBC/ODBC
>  * Binary Client Protocol: 
> [https://apacheignite.readme.io/docs/binary-client-protocol#section-handshake]
>  * Thin clients (Java and Net)
>  * REST protocol - [https://apacheignite.readme.io/docs/rest-api]
> Set <property name="authenticationEnabled" value="true"/> in ignite 
> configuration when persistence is enabled.
> Talk to [~vozerov] and [~taras.ledkov] to get more details and support. 
> They've been working on this functionality: 
> https://issues.apache.org/jira/browse/IGNITE-7436



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

Reply via email to