Create Your Connected App
- Nickolette De Clerck
- Abraham Lloyd
Admin access to your Salesforce org is required to complete this guide.
Please note that only users with Admin access should perform this activity. Please verify your access with your Salesforce Admin.
APPLIES TO | CUNEIFORM FOR CRM FIELD AND DATA MANAGEMENT
Creating Your Connected App
Cuneiform® for CRM uses a connected app to securely broker Salesforce REST API calls.
Let’s create the Cuneiform for CRM: Connected App that will enable secure data-profiling.
Before completing this guide, please review the Double-check the Connected App Digital Signature Configuration section. It contains instructions describing how to verify that the Connected App is correctly configured with the Cuneiform for CRM: Self-Signed Certificate. This step is critical to the Connected App’s configuration.
Self-Guided Workflow
Detailed Instructions
Cuneiform® for CRM uses a connected app to broker Salesforce REST API calls securely. Let’s create the Cuneiform for CRM: Connected App to enable secure data profiling.
Expand the section below to view the detailed configuration instructions.
Leverage These Field Values When Creating the Connected App
Use the following details to create the connected app. We strongly recommend using the same field names and values listed below. Leave any form fields not mentioned in these two sections blank.
Field Name | Field Value |
|---|---|
Basic Information | |
Connected App Label |
|
API Name |
|
Contact Email | Your Email Address |
Contact Phone | Your Contact Phone Number |
Logo URL |
|
Icon URL |
|
Description |
|
API (Enable OAuth Setting) | |
Enable OAuth Settings | checked |
Use digital signatures | checked |
Callback Url |
|
Selected OAuth Scopes | Full Access (full) |
Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows | checked |
Require Secret for Web Server Flow | checked |
Require Secret for Refresh Token Flow | checked |
Perform the following steps to create your new connected app.
Navigate to the App Manager and Create the Connected App
Type
App Managerin the Quick Find search box from the Setup homepage to filter the left navigation.
Click App Manager in the filtered list.
Click New Connected App.
Type
Cuneiform for CRM: Connected Appin the Connected App Name field.
Type
Cuneiform_for_CRM_Connected_Appin the API Name field.
Avoid Connected App Creation Trouble
By default, once you complete the Connected App Name, this form will automatically populate the API Name field with a reformatted version of that name.
This automatically generated reformatted version of the API name includes a colon (:), which is considered an invalid character and is not supported by the API Name field.
To avoid this error, manually type the suggested API name in the API Name field: Cuneiform_for_CRM_Connected_App
Including the suggested value instead of
Cuneiform_for_CRM_Connected_Appand clicking on the Save button will trigger a form validation exception. This exception will invalidate the association between the uploaded Digital Certificate and the Connected App. To address this, the user will need to edit the Connected App, re-upload the Digital Certificate, and save the Connected App.
For more information on this issue, refer to Connected App Digital Signature Configuration.
Type your email address in the Contact Email field.
Type your phone number in the Contact Phone field.
Copy the URL below and paste it into the Logo Image URL field.
https://lh6.googleusercontent.com/ykSeeKgrxYndJj37ia2PoGx9-czBfgSk4jsTpYfUKG96l9k-Bp-NTfhdsNxyyC4hyIQ=w2400
Copy the URL below and paste it into the Icon URL field.
https://lh6.googleusercontent.com/3b6tVui747u3ty6d98JfkXTJCF5unEj6W2oOMs-upvatI0-ydNTA3k1b6Z1cJZOXQ8A=w2400
In the Description field, input:
This Connected App is leveraged by the PeerNova: Cuneiform for CRM application to provide secure access to Salesforce REST APIs.
Check Enable OAuth Settings.
Input the URL below in the Callback URL field.
https://cuneiform-crm.peernova.io/
Configure the Connected App Digital Signature
Check Use digital signatures.
The self-signed certificate you upload to your connected app acts as a public key and is enriched by details that can be used to verify a signature provided by another system. Checking this checkbox will expose a file upload prompt which we’ll use to upload our certificate from this step in the setup process.
Click Choose file and select your self-assigned certificate file from the file upload menu. This file should have a .CRT file extension.
Configure the OAuth Scopes
From Available OAuth Scopes, select Full access (full).
Click the Add button to the right of the Available OAuth Scopes sections to move your selection to the Selected OAuth Scopes.
Repeat the previous step with the Manage user data via APIs (api) and Perform requests at any time (refresh_token, offline_access) OAuth Scopes.
Confirm you've added the correct OAuth Scopes:
Full Access (full)
Manage user data via apis (api)
Perform Requests at Any Time (refresh_token, offline_access)
Check Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows.
Check Require Secret for Web Server Flow.
Check Require Secret for Refresh Token Flow.
Save and Persist the Connect App Configuration
Scroll down and click Save.
Click Continue, which acknowledges that creating the connected app in the Salesforce org will take up to ten minutes.
Confirm that the new connected app has the correct details, and make sure the digital certificate details appear beneath the API (Enable OAuth Settings) section. Please note that any changes to the connected app can take up to ten minutes to take effect.
Double-check the Connected App Digital Signature Configuration
We’ve received reports from customers and our internal testing team that Connected App digital signatures do not consistently persist when the App is first created. Please use the screenshots below to verify that the App has been configured with a digital certificate.
 No Digital Certificate Present |  Digital Certificate is Present |
If no digital certificate is configured with the Connected App, refer toConnected App Digital Signature Configuration for more information on the (now resolved) bug and workaround.
Nice work! You’re now ready for the next two Connected App configuration steps: Configuring OAuth Policies and Permission Sets for Your Connected App.
Configuring OAuth Policies and Permission Sets for Your Connected App
With the Connected App created, the app’s policies must now be configured to define what users can leverage and what session behavior will be enforced.
Let’s define the policies that will govern access and session management for the Connected App.