Token-Based Authentication

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:

• Country
• URL
• Host
• Referrer
• IP address
• Protocol

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

• Walkthrough
• Basic Setup and Usage
• Encryption Key
• Applying Token-Based Authentication by Folder
• Applying Token-Based Authentication by Request Type (Rules Engine)

• Tokens

  • Download Binaries
  • View Source Code (https://github.com/Edgecast/ectoken)
  • Token Generation
  • Token Decryption
  • Token Parameters
• Quick Reference

Edgecast CDN