Adding IP Ranges for Salesforce Sessions with Sonar

 

Adding IPs to the Login IP ranges

If Login IP ranges are set up for the profile of the Salesforce user who is authenticated, then 3 additional IPs have to be added to the IP range.  The reason for this is that Sonar is logging in as the user from the Sonar Servers.

US instance

If you are using our US-based instance the IPs are:

• 3.92.252.114
• 3.230.112.52
• 44.207.138.64

*Note: The Start and End IP address in the Salesforce configuration will be the same values. 

EU instance

If you are using our EU-based instance the IPs are:

• 3.69.107.46
• 18.158.30.178
• 3.126.244.179

*Note: The Start and End IP address in the Salesforce configuration will be the same values.

Where to Whitelist:

For the entire org:

1. Navigate on Setup in Salesforce
2. Search "Security Control" and navigate to Network Access
3. Create a New Trusted IP Range
4. Enter the ranges above

For the profile:

1. Navigate on Setup in Salesforce
2. Search "Profiles" and navigate to Profiles
3. Click on the specific profile you'd like to add an IP Range to
4. In the "Login IP Ranges" section, click New
5. Enter the ranges above

Session Settings and Enforce login IP ranged on every request

In the Session Settings (in the Org Setup) there is an option called "Enforce login IP ranges on every request".  If this is checked on, then as the name implies the IP is checked on every request, not just at login.

Session Settings and Lock sessions to the IP address from which they originated 

There is another setting that affects the sync from Salesforce to Sonar.  If the setting "Lock sessions to the IP address from which they originated" is checked, the sync will fail. With this item checked, it is not possible to run the sync. 

Check out this Salesforce help article to understand more.