NiFi : InvokeHttp, authenticate to Salesforce's Bulk API V 2 , Oauth 2

Question

Hello everyone,

I am trying to authenticate with InvokeHttp NiFi Processor to Salesforce by using Bulk API v2 and with OAuth 2.0 :

ck_sadchaouche_6-1606816870985.png

The InvokeHttp Processor is configured as follow :

ck_sadchaouche_7-1606817038511.png

The Remote URL is made by using this syntax:

https://< mydomain >.salesforce.com/services/oauth2/token?grant_type=password&client_id=<client_id>&client_secret=<client_secret>&username=<username>&password=<password + key>

As we are using the HTTPS protocol, we add a “SSL Context Service” by setting a new “SSL Context Controller Service”:

ck_sadchaouche_8-1606817459585.png

And the Post request is already tested and worked with Postman tool, by responding with an authentication token.

The blocking point for this use case is that, with InvokeHTTP NIFI Processor we have not been able to get a response from the Bulk API ( the first image show that we never receive any response from Salesforce )

If you have any suggestion, it's will be helpful.

Thank you in advance

KSAD

Ksad · Accepted Answer

@stevenmatisonthe solution that i find is to get the Oauth2 token from slaesforec by using command Curl. like is explained in this page : https://www.jitendrazaa.com/blog/salesforce/using-curl-with-salesforce-rest-api/

So i create a ExecuteProces NiFi Procesor. And as parameter i put :

the file C:/loginInfo.txt contains :

grant_type=password&

client_id= 3MVG9iTxZANhwsdsdsdsdspr0LstjR3sRat &

client_secret=21961212323233121943 & username=jitendra.zaa@demo.com &

password=myPWDAndSecurityToken

and the i get a response with the authentication token 🙂

(you can use the cmd command Curl -x post -d @LoginInfo.txt Https://test.salesforce.com/.... to test the connection between the local machine and salesforce )

stevenmatison · Answer

@Ksad Excellent work to completely show us what you have. Also, excellent work to test and confirm your request work in postman first. This is always one of the first things I do to make sure i have a valid test connection and all settings to connect to the API before attempting with InvokeHttp. When you take this route, and you cannot get a response, this indicates a networking issue with Nifi to [salesforce domain]. You should test command line from NiFi node to [salesforce domain] using curl, wget, telnet, etc. Next if you can confirm connectivity, attempt to adjust the processor time outs. Some systems need longer than defaults. For example I sometimes set to 50 and 150 by just adding a 0 to the 2 values (connection and read timeout). f it did time out it should throw an error. You can also set the processor log level to debug to expose more verbose output in the NiFi UI. Last but not least, tail the nifi-app.log file while doing all nifi flow debugging. Sometimes more useful information is found there.

If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.

Thanks,

Steven

Sign up

Please use your Cloudera account.

Login to the community

Please use your Cloudera account.