on 11-11-2022 06:41 AM
With the Custom CData Connector, you can use a CData JDBC driver to ingest data from any of the over 200 databases, applications, and object stores supported by CData JDBC drivers. In this article, we are concerned with establishing a connection to SalesForce. However, these steps can also be used for other drivers with a few changes depending on each driver.
There are two sides to establishing an OAuth connection for CData SalesForce JDBC Connector. One is from the datasource side and the other is from Incorta's side.
First, we need to generate a ClientID and Client Secret from the datasource side.
https://test123.cloud2.incorta.com/incorta/service/datasource/oauthRedirect
Please note that OAuth works in different ways, however, Incorta only supports authorization applications and does not support direct access tokens. Therefore, some of the options suggested in the CData documentation may not work with Incorta. It is recommended to use authorization apps where you provide a CallBackURL and generate a ClientID and Client Secret and then use them within Incorta.
Second, establishing the connection from Incorta
cdata.jdbc.salesforce.SalesforceDriver
jdbc:salesforce:callbackurl=https://test123.cloud2.incorta.com/incorta/service/datasource/oauthRedirect;
jdbc:salesforce:callbackurl=https://test123.cloud2.incorta.com/incorta/service/datasource/oauthRedirect;Logfile=/home/incorta/IncortaAnalytics/salesforce.log;
jdbc:salesforce:callbackurl=https://test123.cloud2.incorta.com/incorta/service/datasource/oauthRedirect;Logfile=/home/incorta/IncortaAnalytics/salesforce.log;verbosity=2;
Please note that these logs need backend access and thus are not accessible by Cloud Customers and are only accessible to Cloud and Support teams for debugging purposes.You have successfully connected to SalesForce. You can now create a new schema and specify the datasource we just created and add the desired tables to your schema.
Note: These steps work for most CData connectors that require OAuth and has already been tested on release 2022.10.0.
Great article @doaa_elhadba