Security and Authentication

To protect data from unauthorized access, Eloqua data stores require connections to be authenticated with an access token or user credentials. Some data stores also require connections to be encrypted using the Secure Sockets Layer (SSL) protocol. The Simba Oracle Eloqua ODBC Connector provides full support for these authentication protocols.

Note:

In this documentation, "SSL" refers to both TLS (Transport Layer Security) and SSL (Secure Sockets Layer). The connector supports up to TLS 1.2. The SSL version used for the connection is the highest version that is supported by both the connector and the server.

The connector uses basic authentication or OAuth 2.0 protocol for authentication and authorization. To use basic authentication, set the authentication method to Basic or Basic Authentication and then, provide your user name and password in the DSN or connection string. Or, you can authenticate your connection through OAuth 2.0 by specifying an access token, or by providing your Eloqua credentials so that the connector retrieves and uses the corresponding access token. For detailed configuration instructions see Configuring Authentication.

Additionally, the connector supports SSL connections with or without one-way authentication. If the server has an SSL-enabled socket, then you can configure the connector to connect to it.

It is recommended that you enable SSL whenever you connect to a server that is configured to support it. SSL encryption protects data and credentials when they are transferred over the network, and provides stronger security than authentication alone. For detailed configuration instructions, see Configuring SSL Verification.