Last update:2026-10-19 14:33:20
Access Control restricts access to live streams by client IP address, HTTP Referer, HTTP User-Agent, URL signature, or the result returned by your authentication server. For rule-based controls, use a directory, file type, or URL pattern to define the scope and a priority value to set the evaluation order.
Available controls depend on the domain role and stream ingest mode. Ingest domains provide IP Access Control, Token Authentication, and Remote Authentication; Referer and User-Agent controls apply to delivery domains.
| Control | What it filters |
|---|---|
| IP Access Control | Client IP address or CIDR block |
| Referer Access Control | HTTP Referer header |
| User-Agent Access Control | HTTP User-Agent header |
| Token Authentication | Signed token and timestamp in the URL |
| Remote Authentication | Your authentication server’s response |
Note: When using Referer or User-Agent access control, we recommend disabling RTMP in Delivery Protocols. RTMP does not support these header-based controls.
IP Access Control allows or blocks requests by client IP address. Use CIDR notation to specify an address range.
| Option | Target | Scope value format |
|---|---|---|
| Specific Directory | Files under the specified path | Path starts and ends with /. Enter one path per line. Example: /live/ |
| Specific File Type | Files with the specified extension | Enter extensions without dots, separated by semicolons (;). Example: flv;m3u8;ts |
| URL Regular Expression | URLs that match a regular expression | Enter the URL path regular expression. Example: live/.*\.(m3u8\|flv)($\|.*) |
Important: Only one allowlist rule is supported. If you need to allow multiple entries, add all entries to the same allowlist rule.
;). The field supports up to 65,535 characters, or about 3,000 IP addresses. You can also choose Import TXT to import entries from a text file.10.Referer Access Control allows or blocks requests based on the HTTP Referer header. Use it to restrict which websites can embed or link to your live streams.
Important: Only one allowlist rule is supported. If you need to allow multiple entries, add all entries to the same allowlist rule.
Set Use Regular Expression:
Enter Referer values based on the selected mode.
Domain names and full URLs
| Field | Format | Example |
|---|---|---|
| Blocked/Allowed Referers (Domain Only) | Domain names without http:// or https://, one per line |
www.example.com |
| Blocked/Allowed Referers (Full URL) | Full URLs starting with http:// or https://, one per line |
https://www.example.com/player |
Regular expressions
Enter one regular expression per line, for example, ^https?://www\.example\.com/.*.
Referer header are allowed.10.User-Agent Access Control allows or blocks requests based on the HTTP User-Agent header.
Important: Only one allowlist rule is supported. If you need to allow multiple entries, add all entries to the same allowlist rule.
10.Token Authentication validates the signature and timestamp in the request URL before allowing access. Configure the same parameter names, key, timestamp format, and component order in your URL signing logic.
| Field | Required | Default | Description |
|---|---|---|---|
| Signature Parameter Name | No | token |
URL query parameter that carries the signature. |
| Timestamp Parameter Name | No | time |
URL query parameter that carries the timestamp. |
| Signing Key | Yes | — | Signing key. If you enter multiple keys, separate them with semicolons (;). |
| Timestamp Format | Yes | Unix Timestamp | Timestamp format. Options include Unix Timestamp and Hexadecimal. |
| Token Validity Period | Yes | — | Token validity duration in seconds. Maximum: 31536000. |
| Signature Input Order | Yes | KEY+PATH+TIME |
Order used to concatenate the key, URI path, and timestamp before generating the signature. |
| Option | Concatenation order |
|---|---|
KEY+PATH+TIME |
key → URI path → timestamp |
KEY+TIME+PATH |
key → timestamp → URI path |
PATH+KEY+TIME |
URI path → key → timestamp |
PATH+TIME+KEY |
URI path → timestamp → key |
TIME+PATH+KEY |
timestamp → URI path → key |
TIME+KEY+PATH |
timestamp → key → URI path |
Remote Authentication validates stream ingest and delivery requests. The CDN forwards request parameters to your authentication server and allows or denies access based on its response.
Note: Remote Authentication is not available for HLS origin-pull domains.
https://auth.example.com/api/check?service=live.| Option | Behavior |
|---|---|
| Forward All | Forward all query parameters from the original request URL. |
| Forward None | Do not forward original query parameters. |
| Forward Selected | Forward only the specified query parameters. |
| Variable | Default parameter name | Description |
|---|---|---|
| Client IP | ip |
Client IP address. |
| Stream Name | streamName |
Live stream name. |
| Stream Type | type |
Stream request type. |
| Host | host |
Original request hostname. |
| CDN Edge IP | cdnip |
CDN edge node IP address. |
| Application name | appName |
Application name in the stream URL. |
| CDN Server IP | serverIp |
CDN server IP address. |
| Request URL | url |
Original request URL. |
| Request Referer | referer |
Original request Referer header. |
;).1 to 10 seconds. The default value is 5.0 to 5. The default value is 0.After confirming a rule or changing a switch, review the configuration. Save Draft saves your work as a draft. To continue through review and submission, choose Next and follow the console prompts. Before testing, check the domain’s configuration status and confirm that the changes have taken effect.
Remote Authentication also requires a supported domain type, as described above.
| Feature | HLS | DASH | HTTP-FLV | WebRTC | RTMP |
|---|---|---|---|---|---|
| IP Access Control | ✓ | ✓ | ✓ | ✓ | ✓ |
| Referer Access Control | ✓ | ✓ | ✓ | ✓ | ✗ |
| User-Agent Access Control | ✓ | ✓ | ✓ | ✓ | ✗ |
| Token Authentication | ✓ | ✓ | ✓ | ✓ | ✓ |
| Remote Authentication | ✓ | ✓ | ✓ | ✓ | ✓ |