Altair® Monarch®

 

Connector Dialog for Salesforce

Enter values into the dialog box to connect and fetch data from your Salesforce source.

Options

Field

Description

Login Server

The name of the server or domain containing Salesforce.

By default this is: login.salesforce.com.

Username

A valid Username for the Salesforce account.

Note: Ensure that the user has API access to the Salesforce organization to which it is associated.

Password

Enter the password for the Salesforce account with your Salesforce Security Token appended right after it.

For example: if your password is mysecretpassw@rd and your security token is 11111111111111111, you would enter mysecretpassw@rd11111111111111111 into this box.

Note: You can reset your security token from the Salesforce settings and have it sent to you via e-mail.

Security Token

Enter the case-sensitive alphanumeric key that is used in combination with your password to access Salesforce.

Connect

Click this button after you have specified the Server, Username, and Password. You can select a Source Type after you have successfully logged-on.

Source
 Type

Select a source type for the data retrieval:

  • Salesforce Objects Table: these are the various Salesforce objects in your organization.

  • Report: list of reports that the user has access to.

Note that Salesforce limits the acquisition of reports to 2000 detail records.

After you select a Source Type, select the data:

  • For Salesforce Objects Table, select the table to which you want to connect.

  • For Report, you can select the report folder in the left pane which contains the report, or the desired report in the right pane.

Preview Data

Click to fetch data using the credentials and criteria you have specified. 10 records are displayed to allow you to verify that you are selecting the correct data.

 

Cconnecting to a SalesForce instance via OKTA authentication with MFA using CData driver.

Here is a snippet of CDATA driver documentation to authenticate with Okta.

 

§  User – Okta user account

§  Password

§  SSSOLoginUrl – You can ask your SSO Team for this info or you can check it in your salesforce instance.

§  SSSOExchangeUrl – You can find this information in SalesForce

§  SSOProperties – This is where you will specify other properties:

o   MFAType – value could either be one of [Email | SMS]

o   MFAPasscode – the actual passcode sent by OKTA

 

To get the information that you need, login to your SalesForce go to your Profile > Settings > Security Control > Single Sign-On Settings

§  SSSOLoginUrl – Identity Provider Login URL

§  SSSOExchangeUrl – OAuth 2.0 Token Endpoint

 

 

 

 

Once you have identify all the information that you need, you can now create an ODBC connection to connect to SalesForce using the latest build of SalesForce CData driver found here http://cdatabuilds.s3.amazonaws.com/support/RFDGA_7998.exe

 

Fill out the following properties:

§  User:

§  Password:

§  SSSOLoginUrl:

§  SSSOExchangeUrl:

§  SSOProperties: MFAType=[Email | SMS]

Hit on “Test Connection” button to request for an MFA code.  Once you received the MFA code, you need to include it in the SSO Properties and try connecting again, you should received a “Test Successful” message.

§  User:

§  Password:

§  SSSOLoginUrl:

§  SSSOExchangeUrl:

§  SSOProperties: MFAType=[Email | SMS];MFAPassCode=<code>

 

Once connection has been established, the session token is valid for two hours before expiring.  You will be asked to provide a new MFA Pass Code once you try to connect again with an invalid session token.  The session token will be stored in in a CredentialsFile such that it is created by default in "%APPDATA%\\CData\\Salesforce Data Provider\\CredentialsFile.txt" and is controlled by the "CredentialsLocation" connection property.

 

 

Connecting to SalesForce via ODBC CData Driver

Using ODBC as DPS Data Source

1.      Create an ODBC Connection following the steps above and make sure access token is valid.

2.      Open DPS and create an ODBC as data source and choose the ODBC you recently created.

3.      Make sure to supply your email and password as specified in your ODBC connection.

4.      Test Connection and Load Tables to get all the tables available.

 

e)