Platform integration and transferring data
Oracle Eloqua offers several integration tools, apps, and APIs to enhance your organizational capability, enrich your data, and improve segmentation. The following outlines features to help secure these integrations.
Data imports and exports
Oracle Eloqua allows you to export contact or account data using any of the following methods:
- From a segment
- Using the data export tool
- Using the Bulk API
Oracle Eloqua supports the use of a Secure File Transfer Protocol (SFTP) server to store imported and exported files and uses SSH keys to authenticate access to the server.
In addition, Oracle Eloqua restricts the size of imported files to 5 GB. When importing Microsoft Excel files, Oracle Eloqua does not evaluate functions and only reads values.
Learn more about data import and export options and SSH Key Configuration.
CRM integrations
Oracle Eloqua CRM integrations use HTTP Basic Authentication. All communications with the CRM are over SSL/TLS connections. Secure connections support 128-bit and 256-bit ciphers.
Important: All Oracle Eloqua customers who are currently using the native integration for Microsoft Dynamics, with either Online (Office 365) or Online (Windows Live) as the authentication type, will need to authenticate all Integration users via OAuth to ensure their users can continue using the integration. OAuth authentication will need to be completed by February 10, 2021 to continue to leverage the functionality. See the product notice to learn more.
Oracle Eloqua developer framework
Authentication
Access to the Oracle Eloqua Bulk API requires adequate permissions based on security group. Oracle Eloqua utilizes SSL/TLS with support for 128-bit and 256-bit ciphers to securely transmit traffic in all API calls. The encryption level depends on the libraries being used by your app.
Oracle Eloqua supports two methods of authentication:
- HTTP Basic Authentication: Authenticates REST API requests by using an authentication header, with a base-64 encoded value.
- OAuth 2.0: Enables the safe retrieval of secure resources while protecting user credentials. Some apps may need to authenticate during the configuration phase and others may need OAuth only when a user invokes a service.
Learn more about the Bulk API.
OAuth signing
Oracle Eloqua signs all outgoing calls with OAuth 1.0a so the receiving system, such as an app, can validate that the call was sent by Oracle Eloqua. As an app provider, it's your responsibility to ensure the validity of all inbound calls to your app. Validation should be performed on every inbound call your app receives with OAuth parameters.