Following the Composer 8.298 release, Salesforce administrators must update the OAuth policy settings for the Composer Connected App. Until this change is made, Composer merges may fail or return authentication errors.

Who is affected: Salesforce orgs running Conga Composer 8.298 or later that have not yet updated their Connected App settings.

Required action: A Salesforce System Administrator must complete the steps below.

Step 1 — Identify the Connected App in use

1. Log into Salesforce as a System Administrator.

2. Go to Setup (gear icon, upper right).

3. Open Custom Metadata Types.

4. On Composer Setting, click Manage Records.

5. Click Settings.

6. Click the value in the Connected App Setting field.

7. Note the Connected App Name — this is the API name of the Connected App used for standard Composer merges.

Step 2 — Update policy settings for the "Composer [NA/EU/AP] for Salesforce" app

1. In Setup, open Manage Connected Apps.

2. Locate the app identified in Step 1 and click Edit. (If you use the Composer Lightning Component, repeat these steps for the Composer Lightning for Salesforce app.)

3. Set Permitted Users to Admin approved users are pre-authorized.

4. Click OK to accept the security warning.

5. Set IP Relaxation to Relax IP Restrictions. (If IPs must stay enforced, add the Conga Composer IP addresses instead.)

6. Click Save.

7. Under Profiles, click Manage Profiles and add all profiles that will use Composer.

References

How to tell which Connected App is in use
Connected App Name Changes after Composer 8.298 Update (with screenshots)

No further action is required once the configuration is updated. If issues persist, contact Conga Support.