ℹ️Introduction

Integrating Salesforce with Neomir DQ enables secure and efficient access to your Salesforce data using modern OAuth-based authentication. This guide walks you through the necessary configuration steps in your Salesforce instance, such as setting up CORS, creating a connected app, and defining policies. Once completed, your Salesforce environment will be ready for seamless integration with Neomir DQ via the client credentials flow — allowing automated, secure, and scalable data access without requiring user interaction.

🔬Details & Information Security

The integration of Neomir DQ with your Salesforce system follows our core principle, that Neomir’s infrastructure never sees, processes or saves your source system’s raw data. The following diagram shows how the integration works once it is setup:

Salesforce Connector UML Diagram.png

🧭Step-by-step Guide

<aside> 💡

To follow this guide, you must be signed in to your Salesforce instance with a user that has the following permissions:

You can check whether your user has this authorization by looking at the “General User Permissions” & “Administrative Permissions” of the profile that is assigned to your user.

</aside>

1. Define CORS Settings

  1. Search Setup for “CORS” and open the shown result

    image.png

  2. Add the following allowed origins:

    https://*.neomir.app
    https://*.neomir.dev
    <https://neomir.app>
    <https://neomir.dev>
    
  3. Enable CORS for OAuth Endpoints

    image.png

    image.png

  4. Your CORS settings should now look something like this:

    image.png

2. Creating a new connected app

  1. In the setup navigation pane, open “Platform Tools —> Apps —> App Manager”

    image.png

  2. At the top left corner, click “New Connected App” and continue

    image.png

  3. Fill “Basic Information”

    image.png

  4. Define API OAuth Settings as follows:

    Enable OAuth Settings:

    Callback URL: https://login.salesforce.com/services/oauth2/callback

    Selected OAuth Scopes:

    “Access the Salesforce API Platform (sfap_api)”

    “Manage user data via APIs (api)”

    “Perform requests at any time (refresh_token, offline_access)”

    Require Proof Key for Code Exchange:

    Require Secret for Web Server Flow:

    Require Secret for Refresh Token Flow:

    Enable Client Credentials Flow:

    image.png

  5. Click “Save”, then “Continue”

  6. Click “Manage Consumer Details”

    image.png