salesforce_security_impl_guide
salesforce_security_impl_guide
salesforce_security_impl_guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuring Salesforce Security Features<br />
Restricting Login To Trusted IP Ranges for Your Organization<br />
However, ranges like 0.0.0.0 to 2.255.255.255 or 132.0.0.0 to 134.0.0.0 are too large.<br />
The start and end IP addresses in an IPv6 range must include no more than 79,228,162,514,264,337,593,543,950,336 addresses (2 96 ,<br />
a /32 CIDR block). For example, the following range is valid: 2001:8000:: to<br />
2001:8000:ffff:ffff:ffff:ffff:ffff:ffff. However, ranges like :: to<br />
ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff or 2001:8000:: to 2001:8001:: are too large.<br />
4. Optionally, enter a description for the range. For example, if you maintain multiple ranges, enter details about the part of your network<br />
that corresponds to this range.<br />
5. Click Save.<br />
Note: For organizations that were activated before December 2007, Salesforce automatically populated your organization’s<br />
trusted IP address list in December 2007, when this feature was introduced. The IP addresses from which trusted users had already<br />
accessed Salesforce during the past six months were added.<br />
Note: Both IP addresses in a range must be either IPv4 or IPv6. In ranges, IPv4 addresses exist in the IPv4-mapped IPv6 address<br />
space ::ffff:0:0 to ::ffff:ffff:ffff , where ::ffff:0:0 is 0.0.0.0 and ::ffff:ffff:ffff is<br />
255.255.255.255. A range can’t include IP addresses inside of the IPv4-mapped IPv6 address space if it also includes IP<br />
addresses outside of the IPv4-mapped IPv6 address space. Ranges such as 255.255.255.255 to ::1:0:0:0 or :: to<br />
::1:0:0:0 are not allowed. You can set up IPv6 addresses in all organizations, but IPv6 is only enabled for login in sandbox<br />
organizations from the Spring ’12 release and later.<br />
82
Change language