请选择
Edge Acceleration
  • Site Acceleration
    • Overview
    • Access Control
      • Token Authentication
    • File Optimization
      • Smart Compression
    • Network Optimization
      • HTTP/2
      • HTTP/3(QUIC)
        • Overview
        • Enable HTTP/3
        • QUIC SDK
          • SDK Overview
          • SDK Download and Integration
          • Sample Code
            • Android
            • iOS
          • API Documentation
            • Android
            • iOS
      • IPv6 Access
      • Maximum Upload Size
      • WebSocket
      • Client IP Geolocation Header
      • Client IP Geographical Location
      • gRPC
    • URL Rewrite
      • Access URL Redirection
      • Origin-Pull URL Rewrite
    • Modifying Header
      • Modifying HTTP Response Headers
      • Modifying HTTP Request Headers
    • Custom Error Page
    • Request and Response Actions
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
  • Smart Acceleration
  • L4 Proxy
    • Overview
    • Creating an L4 Proxy Instance
    • Modifying an L4 Proxy Instance
    • Disabling or Deleting an L4 Proxy Instance
    • Batch Configuring Forwarding Rules
    • Obtaining Real Client IPs
      • Obtaining Real TCP Client IPs via TOA
      • Obtaining Real Client IPs Through Protocol V1/V2
        • Overview
        • Method 1: Obtaining Real Client IPs Through Nginx
        • Method 2: Parsing Real Client IPs on Application Server
        • Format of Real Client IPs Obtained Through Proxy Protocol V1/V2
      • Transmitting Client Real IP via SPP Protocol
  • Edge DNS
    • Hosting DNS Records
      • Modifying DNS Servers
      • Configuring DNS Records
      • Advanced DNS Configuration
    • Domain Connection
      • Adding A Domain Name for Acceleration
      • Ownership Verification
      • Modifying CNAME Records
    • Domain alias
      • Overview
      • Configuration Guide
      • Batch Connecting SaaS Domain Names
      • Configuring Alias Domain Names for Disaster Recovery
    • Traffic Scheduling
      • Traffic Scheduling Management
    • Origin Configuration
      • Load Balancing
        • Overview
        • Quickly Create Load Balancers
        • Health Check Policies
        • Viewing the Health Status of Origin Server
        • Related References
          • Load Balancing-Related Concepts
          • Introduction to Request Retry Strategy
      • Origin Group Configuration
      • Origin-pull configuration
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
      • Related References
        • ld Version Origin Group Compatible Related Issues
        • VOD Origin Server Details
      • Collect EdgeOne origin-pull node IP
  • Edge Cache
    • Overview
    • EdgeOne Cache Rules
      • Content Cache Rules
      • Cache Key Introduction
      • Vary Feature
    • Cache Configuration
      • Custom Cache Key
      • Node Cache TTL
      • Status Code Cache TTL
      • Browser Cache TTL
      • Offline Caching
      • Cache Prefresh
    • Clear and Preheat Cach
      • Cache Purge
      • URL Pre-Warming
    • How to improve the Cache Hit Rate of EdgeOne
  • Rules Engine
    • Overview
    • Supported Matching Types and Actions
    • Rule Management
    • variables
  • Image Processing
Docs Overview/
Edge Acceleration/
Site Acceleration/
Access Control/
Token Authentication/

Token Authentication

Overview

Token authentication is a simple and reliable access control policy that verifies URL access through authentication rules, effectively preventing malicious brushing of site resources. The usage of this feature requires the cooperation of the client and EdgeOne. The client is responsible for initiating an encrypted URL request, and EdgeOne is responsible for verifying the validity of the URL based on pre-set rules.

Principle

The implementation of Token authentication mainly consists of the following two parts:
Client: Initiate an authentication URL request based on authentication rules (including authentication algorithm and key).
EdgeOne node: Verify the authentication information (md5 string + timestamp) in the authentication URL. When the authentication information passes the verification, the access request will be considered as a valid request, and the node will respond normally. If the verification fails, the node will reject the access and directly return 403.

Token Authentication URL Generation and Verification Tool

EdgeOne provides a generation tool and verification tool for Token authentication URLs. Developers can use this tool to quickly and accurately generate and verify hotlink protection URLs that meet the requirements.

Directions

1. Log in to the EdgeOne console. In the left sidebar, click Site List. In the site list, click the site to be configured.
2. On the site details page, click Site Acceleration to go to the global site configuration page, and then click the Rule Engine tab.
3. On the rule engine management page, click Create Rule and select Add Blank Rule.
4. On the rule editing page, set the matching conditions that trigger this rule.
5. Click Action > Select Box, and select Token Authentication in the pop-up action list. The parameter configuration instructions are as follows:
Parameter
Description
Method
Currently, 5 authentication signature calculation methods are supported. Choose the appropriate method based on the access URL format. For details, refer to the authentication method.
Primary key (required)
Primary password, consisting of 6-40 uppercase and lowercase English letters or numbers.
Secondary key (optional)
Secondary password, consisting of 6-40 uppercase and lowercase English letters or numbers.
Authentication encryption string
Authentication parameter name, the value corresponding to which will be verified by the node. It should contain 1-100 characters, including uppercase and lowercase letters, numbers and underscores.
Validity period
The validity period of the authentication URL (1-630720000 seconds). It determines whether a client request is valid:
If the current time is after the ''timestamp + validity period'' time, it indicates that the request has expired, and 403 will be returned directly.
If the current time is before the ''timestamp + validity period'' time, it indicates that the request has not expired, and the md5 string will continue to be verified.

Notes

1. After the request passes the authentication, the node will automatically ignore the authentication-related parameters in the URL to improve the cache hit rate and reduce the amount of origin-pull.
2. The URL cannot contain any Chinese character.