Using a Connection String

For some applications, you might need to use a connection string to connect to your data source. For detailed information about how to use a connection string in an ODBC application, refer to the documentation for the application that you are using.

The connection strings in the following sections are examples showing the minimum set of connection attributes that you must specify to successfully connect to the data source. Depending on the configuration of the data source and the type of connection you are working with, you might need to specify additional connection attributes. For detailed information about all the attributes that you can use in the connection string, see Connector Configuration Options.

Note:

If the server does not support HTTPS connections or SSL verification, then you must disable those features by setting additional properties in your connection string. For more information, see Configuring SSL Verification.

DSN Connection String Example

The following is an example of a connection string for a connection that uses a DSN:

DSN=[DataSourceName]

[DataSourceName] is the DSN that you are using for the connection.

You can set additional configuration options by appending key-value pairs to the connection string. Configuration options that are passed in using a connection string take precedence over configuration options that are set in the DSN.

DSN-less Connection String Examples

Some applications provide support for connecting to a data source using a connector without a DSN. To connect to a data source without using a DSN, use a connection string instead.

The placeholders in the examples are defined as follows, in alphabetical order:

  • [YourAccessToken] is your access token for Eloqua.
  • [YourConsumerKey] is the consumer key associated with your Eloqua application.
  • [YourConsumerSecret] is the consumer secret associated with your Eloqua application.
  • [YourInstanceUrl] is the IP address or host name of the Eloqua server.
  • [YourPassword] is the password corresponding to your user name.
  • [YourPath] is the full path of the .pem file containing trusted CA certificates for verifying the server during SSL authentication.
  • [YourRedirectUri] is base redirect URI for OAuth 2.0 authentication.
  • [YourUserName] is site name and user name that you use to access Eloqua, written in this format: [SiteName]\[UserName].

Connecting to Eloqua Using Basic Authentication

You can connect to the data source using basic authentication through either SQLBrowseConnect or SQLDriverConnect. The following is the format of a DSN-less connection string for connecting to Eloqua using basic authentication:

Driver=Simba Eloqua ODBC Driver;Host=[YourInstanceUrl];Auth_Type=Basic;UID=[YourUserName];PWD=[YourPassword];

For example:

Driver=Simba Eloqua ODBC Driver;Host=secure.server01.eloqua.com;Auth_Type=Basic;UID=SimpleSiteName\jsmith;PWD=123456;

The connector also supports Basic Authentication as a value for the Auth_Type property. For example, this connection string would work the same way as the previous one:

Driver=Simba Eloqua ODBC Driver;Host=secure.server01.eloqua.com;Auth_Type=Basic Authentication;UID=SimpleSiteName\jsmith;PWD=123456;

Connecting to Eloqua Using Access Token

You can connect to the data source using an access token through either SQLBrowseConnect or SQLDriverConnect. The following is the format of a DSN-less connection string for connecting to Eloqua using access token authentication:

Driver=Simba Eloqua ODBC Driver;Host=[YourInstanceUrl];Auth_Type=Access Token;Auth_AccessToken=[YourAccessToken];

For example:

Driver=Simba Eloqua ODBC Driver;Host=secure.server01.eloqua.com;Auth_Type=Access Token;Auth_AccessToken=a2c4e6g8i9k;

Connecting to Eloqua Using Your Eloqua Credentials

You can connect to the data source using your Eloqua credentials through only SQLBrowseConnect. The following is the format of a DSN-less connection string for connecting to Eloqua using your Eloqua app information. The connector initiates an OAuth 2.0 authentication flow based on your app information and then uses the retrieved access token to authenticate the connection.

Driver=Simba Eloqua ODBC Driver;Host=[YourInstanceURL];Auth_Type=OAuth_2.0;Auth_Client_ID=[YourConsumerKey];Auth_Client_Secret=[YourConsumerSecret];Auth_BaseRedirectURI=[YourRedirectURI];

For example:

Driver=Simba Eloqua ODBC Driver;Host=secure.server01.eloqua.com;Auth_Type=OAuth_2.0;Auth_Client_ID=skroob;Auth_Client_Secret=123456;Auth_BaseRedirectURI=eloqua.domain1.com;

Connecting to Eloqua Using Windows Trust Store

The following is the format of a DSN-less connection string for connecting to the Eloqua server that requires SSL and uses the Windows trust store:

Driver=Simba Eloqua ODBC Driver;Host=[YourInstanceUrl];Auth_Type=Access Token;Auth_AccessToken=[YourAccessToken];SystemTrustStore=1;

For example:

Driver=Simba Eloqua ODBC Driver;Host=secure.server01.eloqua.com;Auth_Type=OAuth_2.0;Auth_AccessToken=
kN9PcyQ9prK4LvL4R+lVE=;SystemTrustStore=1;

The following is the format of a DSN-less connection string for connecting to the Eloqua server that requires SSL and uses the path provided in the TrustCertsPath property:

Driver=Simba Eloqua ODBC Driver;Host=[YourInstanceUrl];Auth_Type=Access Token;Auth_AccessToken=[YourAccessToken];SystemTrustStore=0;TrustCertsPath=[YourPath];

For example:

Driver=Simba Eloqua ODBC Driver;Host=secure.server01.eloqua.com;Auth_Type=OAuth_2.0;Auth_AccessToken=
kN9PcyQ9prK4LvL4R+lVE=;SystemTrustStore=0;TrustCertsPath=C:\Users\JSmith\Desktop\Cert\Eloqua.pem;