You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Ilya Kasnacheev (JIRA)" <ji...@apache.org> on 2018/06/05 10:57:00 UTC
[jira] [Created] (IGNITE-8700) Support Uid/Pwd fields for
authentication in DSN connection strings
Ilya Kasnacheev created IGNITE-8700:
---------------------------------------
Summary: Support Uid/Pwd fields for authentication in DSN connection strings
Key: IGNITE-8700
URL: https://issues.apache.org/jira/browse/IGNITE-8700
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.5
Reporter: Ilya Kasnacheev
Assignee: Igor Sapego
I think Ignite should support *Uid* connection string field in addition to existing *User*, and *Pwd* in addition to *Password*. They should be interchangeable. This will improve user experience of tool users trying our ODBC.
I have reviewed several ODBC implementation for popular data bases WRT authentication.
[Microsoft SQL Server|https://www.connectionstrings.com/microsoft-sql-server-odbc-driver/] uses *Uid* for username and *Pwd* for password
[Oracle|https://www.connectionstrings.com/oracle/] seems to prefer *User Id* and *Password* but also supports *Uid* and *Pwd*.
[IBM DB2|https://www.connectionstrings.com/ibm-db2/] uses *UID* and *PWD*.
[MySQL seems to prefer|https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-without-dsn.html] User and Password, but [seems to also accept|https://www.connectionstrings.com/mysql/] *Uid* and *Pwd*.
[PostgreSQL|https://www.connectionstrings.com/postgresql-odbc-driver-psqlodbc/] uses *Uid* and *Pwd*.
In short, everybody seems to support *Uid* and *Pwd* even if they have their own field names. Many tools (such as Informatica) rely on this convention, translating GUI inputs into *Uid* and *Pwd* connection parameters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)