For more details on CDN's content authentication service, see Authentication Token.

You can restrict or grant access to your content by configuring an authentication IP address or an IP block. . This configuration will affect the entire secure content of your CDN account. Configuring an authentication IP Address does not mean all of your content will be secured. You must place your content in the right directories (/media/securehttp, /media/secureflash, /media/securewm) and you have to use an authentication token. Authentication IP address validation occurs before a token is validated. Consider authentication IP as an additional way to secure your content. You can have up to 20 IP address records. If you want to block access from IP, you can enter "211.37." instead. IP blocks can be specified in the manner of "8bit times n".

{| cellspacing="5" style="width: 40%; border: 0px; margin-left: auto; margin-right: auto; padding: 10px;"
  IP range
  value you will pass to API
  123.123.123. (Allow or Deny a single IP)

IP match starts from higher priority IP to lower and if there is a match, it will stop the process.

You can also set an authentication IP with an * (asterisk). This can be helpful if you want to deny all IP addresses. The example below shows that requests from are allowed and requests from any other IP ranges are blocked.

{| cellspacing="5" style="width: 60%; border: 0px; margin-left: auto; margin-right: auto; padding: 10px;"
  IP Address
  Access Type
  Allow from Netherlands
  Deny all


Creates an authentication IP record
Deletes an authentication IP address.
Edits an authentication IP
Retrieve a SoftLayer_Network_ContentDelivery_Authentication_Address record.
rearranges authentication IPs