> For AI agents: [llms.txt](https://docs.trustedauth.com/llms.txt) provides a Markdown index of this documentation.

# Oracle Eloqua

Oracle Eloqua is a software as a service platform for marketing automation that aims to help organizations manage marketing campaigns and sales lead generation (see <https://www.oracle.com/cx/marketing/automation/>). You can protect access to Oracle Eloqua by integrating Oracle Eloqua with Identity as a Service. Once integrated, users can use single sign-on to log in to their Oracle Eloqua account through Identity as a Service.

note

This integration was tested using Identity as a Service version 5.11 and Oracle Eloqua 20C. Other versions of Oracle Eloqua may require integration and configuration steps that differ from those documented in this procedure. For other versions of Oracle Eloqua, use this procedure as a starting point for integrating Oracle Eloqua. In the event of other issues, contact <support@entrust.com> for assistance.

To integrate Oracle Eloqua with Identity as a Service, complete the following steps.

## Step 1: Export the signing certificate

1. Log in to your Identity as a Service administrator account.
2. Click Menu icon **>** **Security > Applications**. The **Applications List** page appears.
3. Under **SAML Cloud Integrations**, click **SAML Signing Certificates**. The **SAML** **Signing Certificates** page appears.
4. Click the download icon next to the certificate to export the certificate you want to import into your SAML service provider application. The **Export Certificate** dialog box appears.
5. If the certificate has been issued by a CA, do one of the following:
   - Click **Certificate** to export the self-signed certificate.
   - Click **Root CA Certificate** to export a certificate issued from a CA.
   - Click **Certificate Chain** to export the SAML signing certificate and its CA certificates.
6. Click **Export**.

## Step 2: Copy the SAML Configurations from Identity as a Service

1. Log into your Identity as a Service administrator account.

2. Click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.

3. Under **SAML Cloud Integrations**, click **SAML Configuration**. The **SAML Configuration** dialog box appears.

   This dialog box contains information you need to configure your SAML application for Identity as a Service authentication.

4. Do one of the following:

   - Leave this dialog box open to reference later in this procedure.
   - Copy the Entity ID, Single Sign-on URL, and Single Logout URL to a text file and save it to reference later in this procedure.

note

Depending on the integration you are performing, you may not need all three of these SAML configuration values.

## Step 3: Configure Oracle Eloqua SSO certificate

1. Log in to your Oracle Eloqua account.

2. Click the menu icon **>** **Settings** and click **Single Sign On**. The **Single Sign-On** page appears.

3. Click the **Certificates** tab. The **Certificate Management** page appears.

4. Click **Upload Certificate**.

5. Browse to locate the signing certificate you downloaded from Identity as a Service in _Step 1: Download the signing certificate_.

6. Click **Save**.

7. Click the **Certificates** tab. The **Certificate Management** page appears.

8. Click **Create Certificate**.

   Create an Eloqua certificate if an external website needs verification that a request is coming from an Eloqua organization.

   **Example:** `Eloqua_Service_Provider`

9. Click **Save**.

Click the **Certificates** tab. The **Certificate Management** page appears.

Click **Create Certificate**.

Create an Eloqua certificate if an external website needs verification that a request is coming from an Eloqua organization.

**Example:** `Eloqua_Service_Provider`

Click **Save**.

## Step 4: Configure Oracle Eloqua Identity Providers

1. Log into your Oracle Eloqua account.
2. Click the menu icon **>** **Settings** and then click **Single Sign On**. The **Single Sign-On** page appears.
3. Click the **Identity Providers** tab. The **Identity Providers** page appears.
4. Click **Create Identity Provider**. The **Identity Provider Details** page appears.
5. In the **Identity Provider Details** page, do the following:
   1. Enter a **Name** for the Identity Provider. For example, Identity as a Service as a Service Identity Provider.
   2. Enter the **Login URL**. This is the **Single Sign-On URL** you copied in _Step 2: Copy the SAML Configuration_.
   3. Enter the **Logout URL**. This is the **Single Logout URL** you copied in _Step 2: Copy the SAML Configuration_.
   4. In the **Protocol Binding** field, enter **HTTPPost**.
   5. Enter the **Identity Provider Entity**. This is the **EntityID UR**L you copied in _Step 2: Copy the SAML Configurations_.
   6. In the **Identity Provider Certificate** field, click **Manage Certificate** and browse to select the **Identity Provider Signing Certificate** you created in _Step 3: Configure Oracle Eloqua from Identity as a Service_.
   7. Optional. Configure the **User Identity**.
6. Click **Save**.
7. Click the **Identity Providers** tab. The **Identity Providers** page appears.
8. Select the **Identity Provider** you just created and click **Edit**.
9. Under the **Service Provider** section, copy the following to a text file:
   - Service Provider Entity
   - Service Provider Logout URL
   - ACS URL

note

You need this information when you complete _Step 5 : Add Oracle Eloqua to Identity as a Service_.

10. Click **Close**.

## Step 5: Add Oracle Eloqua to Identity as a Service

1. Log into your Identity as a Service administrator account.
2. Click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.
3. Click **Add**. The **Select an Application Template** page appears.
4. Do one of the following:
   - Select **SAML Cloud Integrations** from the search drop-down list and scroll to find the application you want to add to IDaaS.
   - In the **Search bar**, enter a search option to filter for the application you want to add to IDaaS.
5. Click **Oracle Eloqua**. The **Add Oracle Eloqua** page appears.
6. Enter an **Application Name**.
7. Enter an **Application Description**.
8. Optional. Add a custom application logo.
   1. Click Plus icon next to **Application Logo**. The **Upload Logo** dialog box appears.
   2. Click Upload icon to select an image file to upload.
   3. Browse to select your file and click **Open**. The **Upload Logo** dialog box reappears showing your selected image.
   4. If required, resize your image.
   5. Click **OK**.
9. Select the **Authentication Flow** that appears to users during login.
10. Click **Next**. The **General** page appears.
11. If available, use the **Upload Metadata XML** file option to auto-populate the following fields, if available in the file:
    - Default Assertion Consumer Service URL
    - Alternative Assertion Consumer URLs
    - Service Provider Entity ID (Issuer)
    - Single Logout Service URL
    - SAML Signing Certificate
    - SAML NameID Encoding Format
    - SAML Signature Algorithm
12. Click the upload icon to the **Upload Metadata XML** and browse to the location of the metadata file you downloaded. The **Metadata Configuration** dialog box appears.
13. If required, click **Merge with existing values** to merge new values with existing values for Alternative Assertion Consumer Services URLs and SAML attribute names.
14. Click **Save**.
15. If you do not have a metadata file, use the information provided in the next steps to populate the fields.
16. Enter the **Default Assertion Consumer Service (ACS) URL** that you copied in _Step 4: Configure Oracle Eloqua Identity Providers_.
17. Enter the **Service Provider Entity ID (Issuer)** that you copied in _Step 4: Configure Oracle Eloqua Identity Providers_.
18. Optional. Enter the **SAML Username Parameter Name** used to identity the user ID being requested for authentication. The user ID can then be passed as a parameter, for example, Username=jdoe. Alternately, if the SAML username is NameID, the SAML Request XML NameID element value is used to the identify the IDaaS userID.
19. Enter the **SAML Session Timeout** to the time when the SAML Assertion times out. The maximum is 720 minutes.
20. From the **SAML Name ID Attribute** drop-down list, select the user attribute that will be used to uniquely identity a user to both Identity as a Service and the application. The attribute should be one that will never change.
21. Select the **SAML Signing Certificate** from the drop-down list.
22. Optional: Select **Sign complete SAML response** to ensure the message integrity of the SAML response sent to the application during authentication.
23. Deselect **Enable Go Back Button** if you do not want users to be able to go back to the Oracle Eloqua login page to log in.
24. Select **Show Default Assertion Consumer URL Service in the My Profile**. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
25. Optional: Select **Encrypt SAML Assertion**. When selected the SAML Assertion is also encrypted. If you select this option, do the following:
    1. From the **Encryption Method for Key** drop-down list, select either **RSA Version 1.5** or **RSA-OAEP**. RSA Version 1.5 is the default.
    2. From the **Encryption Method for Data** drop-down list, select the encryption method used to encrypt data. The options are:
       - AES-256 (default)
       - AES-128
       - AES-192
       - Triple DES
    3. In the **Encryption Certificate** field, upload the encryption certificate file.

note

The **Subject Domain Name** and **Certificate Expiry Date** values are populated with values from the certificate once the **Encryption Certificate** is uploaded.

26. Optional. Add **Alternative Assertion Consumer Service URLs**, as follows:
    1. Click **Add**.
    2. Enter a **Name**.
    3. Enter a URL **Value**.
    4. Select **Show in My Profile** to display the Alternative Consumer Service URL in a user's My profile page.
    5. Optional. **Add an Application Logo**.
    6. Click **Add**.
    7. Repeat these steps to add more Alternative Assertion Consumer Service URLs.
27. Optional. Add a **Relay State** as follows:
    1. Under **Relay State**, click **Add**. The **Add Relay State** dialog box appears.
    2. Enter a **Name** for the relay state.
    3. Enter the **Value** for the relay state. This setting specifies the application or URL that is a user is redirected to after successful authentication.
    4. Select **Show in My Profile** to display the relay state on the user's My Profile page.

note

After you add relay states, you can also enable or disable them on the Add/Edit application page. Click the disable icon next to the relay state to disable it or click the enable icon to re-enable it. state to disable it. If at any time you want to re-enable it, click the enable icon.

Relay states apply to the Default Assertion Consumer Service URLs and not the Alternative Assertion Consumers URLs.

28. Optional. Upload a Relay State custom logo.
29. Click **Add**.
30. Repeat these steps to add more Relay States.
31. Click **Submit**.

## Step 6: Add a resource rule

See [Create resource rules](/docs/authentication-and-security/create-and-manage-resource-rules.md).

## Step 7: Test the integration

1. Open in a Web browser and enter the Oracle Eloqua URL.
2. On the **Login** page, click **Sign in with SSO or another account** (<https://login.eloqua.com/auth/saml2?ShowError=False&CheckFrame=False>).
3. Sign-in with your company credentials. You are redirected to Identity as a Service.
4. Complete the Identity as a Service authentication.
5. After successful authentication you are redirected to the Oracle Eloqua resource.