Configuring Authentication

Some Spark Thrift Server instances are configured to require authentication for access. To connect to a Spark server, you must configure the Simba Apache Spark ODBC Connector to use the authentication mechanism that matches the access requirements of the server and provides the necessary credentials.

For information about how to determine the type of authentication your Spark server requires, see Authentication Mechanisms.

You can set the connection properties for authentication in a connection string, in a DSN (in the odbc.ini file), or as a connector-wide setting (in the simba.sparkodbc.ini file). Settings in the connection string take precedence over settings in the DSN, and settings in the DSN take precedence over connector-wide settings.

Depending on the authentication mechanism you use, there might be additional connection attributes that you must define. For more information about the attributes involved in configuring authentication, see Authentication Driver Configuration Options on page 1.

The following authentication methods are available:

• Using No Authentication
• Using Kerberos
• Using User Name
• Using User Name And Password
• Using Windows Azure HDInsight Emulator
• Using Windows Azure HDInsight Service
• Using OAuth 2.0 on page 1
• Using an API Signing Key
• Using Token-based Authentication
• Using MapR SASL

If cookie-based authentication is enabled in your Spark Server 2 database, you can specify a list of authentication cookies in the HTTPAuthCookies connection property. In this case, the connector authenticates the connection once based on the provided authentication credentials. It then uses the cookie generated by the server for each subsequent request in the same connection. For more information, see HTTPAuthCookies.

Related topics

• Configuring the Driver on page 1
• Driver Configuration Options on page 1