Protecting Assets Using Both Country Filtering and Token-Based Authentication

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

A Country Filtering and a Token-Based Authentication configuration cannot be applied to the same folder. However, since both of these features are applied recursively, you may apply protection on a hierarchical basis. This can be seen in the following illustration.

This same principle can be used to apply multiple Country Filtering configurations to a particular folder.

In the above example, a Token-Based Authentication configuration has been applied to a folder called "Presentations." The "Presentations" folder contains a folder called "Sales." A Country Filtering configuration has been applied to this subfolder. The "Presentations" folder will be protected by Token-Based Authentication, while the "Sales" folder will be protected by both Token-Based Authentication and Country Filtering.

An asset residing in a folder that is protected by both Token-Based Authentication and Country Filtering cannot be downloaded unless the requirements for both security mechanisms are met. In the above example, content stored in the "Sales" folder cannot be downloaded unless a valid token is provided and the Country Filtering configuration does not prevent users in your country from accessing it.