How to prepare for additional login pools
|Knowledge Article Number||000182187|
Important: This document is for informational purposes only, and is not part of any legal or otherwise binding agreement. The policies and practices described in this document are subject to change at Salesforce's sole discretion.
As an admin of a Salesforce org, you may have end users accessing Salesforce while traveling or working from remote offices. Your organization’s network settings impact their ability to log in from another region of the globe.
Note: If you are following our best practices to allow access to all Salesforce IP ranges, it is likely that no action is required. We updated our network IP ranges in the What Salesforce IP ranges should I whitelist? article in April 2015.
What are login pools and how will this benefit me?
Login pools process all login requests when end users or inbound-traffic integrations attempt to access the Salesforce app. Upon login, end users and integrations will be sent to the nearest data center to be processed, which then verifies credentials and forwards to the appropriate instance.
We’re working to improve your login performance, regardless of which instance you’re logging in from. In the last year, we further improved the resiliency of our infrastructure by adding additional login pools to our AMER and Asia Pacific (APAC) data centers. On November 14, 2015 US Pacific Time, we are adding more login pools to our AMER and EMEA data centers. If your end users are accessing Salesforce from the AMER or EMEA regions, they may authenticate via these new login pools, thus reducing the time it takes to log in.
What action do I need to take?
You will need to take action if both of the following criteria apply to you. Otherwise, no action is necessary.
If your IT department has set up your corporate network settings to restrict access to only certain Salesforce IP ranges, you will need to update your corporate network settings to allow access to all Salesforce data centers.
We recommend that you allow access to all of the ranges for every data center, regardless of where your instance resides. The full list of Salesforce IP ranges is available in the What Salesforce IP ranges should I whitelist? article.
What if I do not take action?
If you do not update your corporate network settings to allow access to all Salesforce IP ranges, and your end users and integrations reference login.salesforce.com, your end users may not be able to log in and your inbound integrations may stop working starting on November 14, 2015 US Pacific Time.
When is this change taking effect?
We’re adding a login pool to our AMER and EMEA data centers on November 14, 2015 US Pacific Time. Please check trust.salesforce.com/trust/maintenance/ for further updates.
How can I get more information?
You can also watch the Login Pools - Will This Change Impact My Company? video. For any additional questions, you can reach out to Customer Support by opening a case via the Help & Training portal.
Technical QuestionsAre you a System Administrator or IT Department? Review the following questions and answers for more technical information.
Do I need to make any changes to the 5 IP addresses for mail relay?
We are not adding additional email relay IP addresses at this time. However, you should still double check that you have whitelisted all five of our email relay IP addresses. Please refer to What Salesforce network IP addresses do I need to whitelist? article.
Do I need to make changes to my integrations?
Yes, please refer to What Salesforce network IP addresses do I need to whitelist? article for more information.
Do I need to restart integrations after the maintenance?
Yes, you'll need to restart integrations after the maintenance. Restarting ensures that the DNS cache is clear.
Do I need to make any changes to the Apex Web Services Generated WSDLs?
No, the Apex Web Services Generated WSDLs do not require any changes.
Does a partner WSDL need to be regenerated after the maintenance?
No, a partner WSDL does not need to be regenerated after the maintenance.
Do I need to make any changes to the Sender Policy Framework (SPF) records?
No, you don't need to make any changes to the Sender Policy Framework records.
Will apps from the AppExchange be impacted by this change?
No, AppExchange apps will be impacted by this change.
Impact to Web-to-Leads/Cases (W2X)?
No, there will not be any impact to W2X.
Impact to Email-to-Case (E2C)?
No, there will not be any impact to E2C.
Impact CTI integrations?
No, this maintenance will not impact CTI integrations.
Are OAuth refresh tokens be affected by this maintenance?
No, OAuth refresh tokens will not be affected by this maintenance.