|
Option
|
Description
|
|
User ID/Password Authentication
|
|
|
Specifies the method the driver uses to authenticate the user to the server when a connection is established.
If set to 0 (User ID/Password), the driver sends the user ID in clear text and an encrypted password to the server for authentication.
If set to -1 (No Authentication), the driver sends the user ID and password in clear text to the server for authentication.
If set to 4 (Kerberos Authentication), the driver uses Kerberos authentication. This method supports both Windows Active Directory Kerberos and MIT Kerberos environments.
Default: 0 User ID/Password
|
|
|
Specifies the UserID used for Impersonation and Trusted Impersonation. When impersonation is enabled on the server, this value determines your identity and access rights to files when executing queries.
Default: None. If no value is provided for this option or if impersonation is disabled, you will execute queries as the user who initiated the HiveServer process.
|
|
|
The default user ID that is used to connect to your database.
Default: None
|
|
|
Additional Properties for Session Cookie Based Authentication (HTTP Mode only)
|
|
|
Specifies the name of the cookie used for authenticating HTTP requests when HTTP mode (TransportMode=1) and session cookie based authentication are enabled (EnableCookieAuthentication=1).
Default: If no value is specified, the driver attempts to use the following cookie names by default:
 hive.server2.auth (Hive connections)
hadoop.auth (Apache Knox connections)
JSESSIONID (Apache Knox connections)
|
|
|
Determines whether the driver attempts to use session cookie based authentication for requests to an HTTP endpoint after the initial authentication to the server. Cookie based authentication improves response time by eliminating the need to re-authenticate with the server for each request.
If set to 0 (Disabled), the driver does not use cookie based authentication for HTTP requests after the initial authentication.
If set to 1 (Enabled), the driver attempts to use cookie based authentication for requests to an HTTP endpoint after the initial authentication to the server. The cookie used for authentication is specified by the Cookie Name option. If the name does not match, or authentication fails, the driver attempts to authenticate according to the setting of the Authentication Method option.
Default: 1 (Enabled)
|
|
|
Option
|
Description
|
|
Specifies the method the driver uses to authenticate the user to the server when a connection is established.
If set to 0 (User ID/Password), the driver sends the user ID in clear text and an encrypted password to the server for authentication.
If set to -1 (No Authentication), the driver sends the user ID and password in clear text to the server for authentication.
If set to 4 (Kerberos Authentication), the driver uses Kerberos authentication. This method supports both Windows Active Directory Kerberos and MIT Kerberos environments.
Default: 0 User ID/Password
|
|
|
The name of the GSS client library that the driver uses to communicate with the Key Distribution Center (KDC).
Default: native (the driver uses the GSS client for Windows Kerberos. )
|
|
|
The service principal name to be used by driver for Kerberos authentication.
Default: None.
|
|
|
The default user ID that is used to connect to your database.
Default: None
|
