Skip to main content
B
Babu Mani
Participant
March 4, 2020
Question

Error configuring Salesforce Integration

  • March 4, 2020
  • 1 reply
  • 1118 views

Error configuring  Adobe Sign Integration with salesforce.

I am trying to install the Adobe Sign from salesforce app exchange amd configure it for a demo. Installation of the app in Salesforce was successful. I am getting an error when Configuring it using the steps mentioned in the Adobe installation steps. It would be great if someone can help me resolve this error. Following are the steps I followed.

  1. Installed the Adobe Sign from Salesforce app exchange. Salesforce is in the latest Spring 2020 version
  2. Created a Adobe Sign Trial Account ad ensured my account is a administrator. Email matched with the salesforce user's email
  3. Added the adobe permission sets to the salesforce user. 
  4. Ensured that both the "Lock sessions to the IP address from which they originated" and the "Lock sessions to the domain in which they were first used" settings in Session Settings are unchecked in Salesforce 
  5. I clicked on the Adobe Sign Admin tab in salesforce and launched the Adobe Sign for Salesforce Setup Wizard
  6. As Step 1 in Wizard, I signed into adobe using the trial account 
  7. Clicked on "Allow Access" when prompted
  8. Then logged in to salesforce again when prompted. After this step I am getting the below error. 

Before proceeding, please ensure that both the "Lock sessions to the IP address from which they originated" and the "Lock sessions to the domain in which they were first used" settings under the Setup > Security Controls > Session Settings are unchecked or toggle the "Timeout Value" between the default (2 hours) to another value of your choice. Error is: settings/Security.settings (Line: 619: Column:22) : Property 'lockerServiceFrozenRealm' not valid in version 33.0

This topic has been closed for replies.

1 reply

J
jali@adobe.com
Participant
March 5, 2020

It seems like Salesforce breaks the backward compatibility in their metadata api calls.

The workaround for this issue is to add the following ip ranges in your org:(setup->security->network access)

<ipRanges>

<start>166.78.79.112</start><end>166.78.79.127</end>

<start>52.71.63.224</start><end>52.71.63.255</end>

<start>52.35.253.64</start><end>52.35.253.95</end>

<start>52.48.127.160</start><end>52.48.127.191</end>

<start>52.58.63.192</start><end>52.58.63.223</end>

<start>207.97.227.112</start><end>207.97.227.127</end>

<start>52.196.191.224</start><end>52.196.191.254</end>

<start>52.65.255.192</start><end>52.65.255.223</end>

<start>13.126.23.0</start><end>13.126.23.31</end>

</ipRanges>

 

J
jali@adobe.com
Participant
March 9, 2020

Hello,

We have opened a case with Salesforce for this problem which is caused by the backward compatibility issue in Salesforce release. They have provided a fix which will effective on Thursday(March 9, 2020).

 

With the fix from Salesforce in your org, you don't need to mannually add the trusted ip ranges above.

 

Thanks.

J
jontowles
Participant
March 12, 2020

This is still an issue today as of 3/11/20.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices