Aurora: Salesforce connector v4.4

Salesforce connector upgrade

With many customers upgrading to Salesforce Hyperforce, where Salesforce IPs change dynamically, there is a risk of  frequent integration failure. 

To mitigate this risk, we have upgraded the Salesforce connector to version 4.4 . 

Now, the authorization request originates from Salesforce to authorize the Salesforce Integration API App configured in the community. After the authorization is successful, the access and refresh tokens are verified and stored in Salesforce. This ensures a stable and seamless integration.

Notes: 

• Contact support to add the required configs in the configuration file.
• The authorization needs to be performed by a member with elevated permissions, for example, an Admin.

This article guides you through:

• Steps to follow in the community
• Steps to follow in the Salesforce App

Steps to follow in the community

Note: The member who performs these steps should have elevated permissions like those of an Admin.

1. Contact support to add the required value to the configuration file.
   The new setting automatically appears in Aurora Admin as shown below.
   
2. Open the drop-down menu for this app (three dots) and select Edit web app. The Edit Web App window opens.
   
3. In the Authorization redirect URL field, enter the redirect URL (or the callback URL).
4. Select Edit.

The entries are saved.

Steps to follow in Salesforce

This section walks you through installing and configuring the Salesforce connector.

1. Navigate to the provided release package URL.
2. Sign in to the Salesforce organization where you will install the connector package.
3. Install the package.
   • Select Install for all users and then select Done.
   • Wait for the success message indicating successful installation.
   • Confirm the package is installed by going to Setup > Installed Packages.
4. Configure remote site settings.
   • Go to Setup > Remote Site Settings.
   • Create a remote site setting for the community integrating with Salesforce.
   • Read more on how to configure Remote Site Settings.
     
5. Set profile permissions. 
   
   • Go to Setup > Manage Users > Profile.
   • Select the profile used for integration.
   • Ensure appropriate Field Level Security Permissions are granted for Standard and custom objects (Account, Case, Contact, Postback Comment, Community Users, Private Message).
6. From the App Launcher, select Khoros Salesforce Integration.
7. Go to Custom Settings > Community Settings > Create.
8. Enter community settings details.
   
   • Community ID: The ID of the integrated application. Find this in the "Community" config in the config file.
   • Client ID: The Client ID of the SalesforceIntegration API App on the community (Admin > Dev Tools > API Apps).
   • Secret: The Secret corresponding to the Client ID.
   • Redirect URL: The URL of the VisualForce page for Custom Settings.
   • Base URL: The community base URL. For subpath-enabled communities, append the subpath.
   • Is Proxy Enabled?: Always select this for Aurora applications.
   • Context Name: Tapestry Context name/Webserver char path. Example: t5/s.
9. Authorize the connection.
   
   • After saving, the connection status shows "Not Active".
     
   • Select Authorize. You are redirected to the Aurora application authorization page.
     
   • Select Authorize. You are redirected to the authentication window. Note: Authorize with an Administrator or a member with admin-like permissions to prevent API call failures.
   • After successful authentication, you are redirected to the custom settings page with the message "TenantId: is successfully authorized."
   • The Connection Status updates to Active. The Username field displays the username used for authorization.
   • This generates Access and Refresh tokens and they are stored in a Salesforce object.

Note: 

• • When the access token expires, the Connection status changes to Halted.
  • A "RefreshAuthToken" link appears. You can always re-authorize by selecting the Authorize link.
  • By default, the refresh token expiry of the salesforceIntegrationApp is set to 5 years.

10. Configure feature settings.

• Select the Feature Settings tab.
• Select Create.
• Enable the required settings and select Save.

 

• Read more about configuring feature settings.

11. (Optional) Enable email notifications.

• To enable Salesforce email notifications for Case Create/Update/Comments, configure email services by going to Setup > Develop > Email Services.

Read more on enabling email notifications.