Show search and navigation.

 

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.
TBAThe Token-Based Authentication feature enforces authentication prior to content delivery. Authentication takes place via an encoded token value that must be included in the request URL. This token value is then decrypted on an edge server. The requested content will only be delivered when the user meets the requirement(s) defined in the token.

Are you looking for our token encryption / decryption binaries or source code?
Download Binaries
View Source Code (https://github.com/Edgecast/ectoken)

The purpose of Token-Based Authentication is to provide a safeguard against hotlinkingRefers to the practice of leveraging content, typically an image, from a different web site without proper consent or authorization. with the purpose of ensuring accurate billing of content delivery. It achieves this goal by requiring requests to contain a token value that defines the criteria that a requester must meet before it can be served via the CDN. This criteria may identify authorized requesters by:

In addition to the above criteria, an expiration date may also be assigned to a token to ensure that a link only remains valid for a limited time period.

Token-Based Authentication only requires authentication for content requested via the CDN. It does not affect links that bypass the CDN by pointing directly to the origin server.

More Information