Salesforce documentation: API guide, Authentication page
- Name (required): Name the connection.
- Connection type (required): The form will automatically select Salesforce.
- Account type (required): Select Production or Sandbox.
- Oauth2 flow type (required): Select JWT bearer token chiefly for server-to-server API integration. This flow uses a certificate to sign the JWT request and doesn’t require explicit user interaction. (Refresh token connections are described separately.)
- Username (required): The username is sent to registered mail after the creation of Salesforce account.
- Click Save & authorize. The following page displays:
- Enter your registered Salesforce account username and password, and click Login to establish the connection.
Read more about this connector:
- Connect Salesforce to Anything
Boost productivity and unlock even more value from your business applications
I previously configured this with a Refresh token and have been running for a couple months; now I am changing it to be a JWT Token. When I click Save & Authorize, it gives me an error:
/!\ Expected field: salesforce.privateKey or salesforce.publicKey to be present.
Tom, It appears the problem is even bigger than I anticipated. This article is referenced by the Integration App, but according to what I learned from Sanjit in the Integration App Group class yesterday, a JWT Bearer token is not a viable option for the connection. One primary reason he gave is that the JWT Bearer token doesn't support the Online status. I have spent a significant amount of time on 3 occasions trying to get this to work because it looked like a better, more robust option for the connection. Will you please add text right up front in this article to help prevent other people from making the same mistake?
(and if I'm wrong, please let me know. I would love to have my system set up as good as possible).
Please sign in to leave a comment.