Unable to successfully connect to Salesforce using Starling Connect connector version 6 and 7 (4380395)

Unable to successfully connect to Salesforce using Starling Connect connector version 6 and 7

With Salesforce connector version six and seven, some changes were made on the connection to the Salesforce api endpoint. Now the connection is made using a private key.

Create a private key to be used with Salesforce

The following Salesforce guides can be used to assist with the creation of the private key

https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_key_and_cert.htm?_ga=2.43114208.439795187.1656333652-1742453021.1655933163

This Salesforce guide can be used on how to setup the connected application to use the private key

https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_connected_app.htm

Once complete the Salesforce connector in Starling Connect will need the complete value of the private key.

 

Two caveats to note:
1)  When using the aud/audience value of the JSON Claims Set (ex. https://login.salesforce.com) for the ‘Token URL’ field in the connector, when it should be the full token endpoint value (ex. https://login.salesforce.com/services/oauth2/token).  
This makes sense in hindsight, but at first it isn’t immediately clear.

2) The Private Key value in the connector needs to include both the Begin and End statements (all the dashes and the wordings "Begin|End Private Key") are all part of the complete value of the private key.
IN ADDITION to removing all hidden characters such as /n new line, /r carriage return, etc.  Certain certificate exports will contain these hidden characters for pleasing visual formatting and a program like Notepad++ or similar that will show all characters as symbols can help here.

Salesforce-Connector-V6