Updated on 2025-07-25 GMT+08:00

Overview

Stream Push Authentication

Media Live provides multiple authentication methods, including URL validation and IP address access control list (ACL), to prevent livestream resource theft. If multiple authentication methods are configured, livestream resources can be accessed only after the access request is approved by all the authentication methods.

The method of configuring stream push authentication is the same as that of configuring playback authentication. For details, see URL Validation and IP Address ACL.

Note:

  • By default, URL validation is not displayed. To use it, submit a service ticket to apply for the permission.
  • If the stream push protocol of an ingest domain name is SRT, the configuration page of URL validation and ACL will be invisible. If you want to enable URL validation for an SRT ingest domain name, you can configure CIDR IP Whitelist and Primary Input Decryption Parameters (with Decryption enabled) when creating a channel. For details, see Creating a Channel.

Playback Authentication

Media Live provides referer validation, URL validation, and IP address ACL to identify and filter out malicious visitors. Only authenticated visitors can use Media Live.

URL validation protects Live origin server resources from unauthorized download and theft. Referer validation uses referer blacklists/whitelists to prevent hotlinking. However, this method is not recommended as the referer content can be forged. You are advised to use URL validation. Table 1 shows the authentication methods of Media Live.

Table 1 Authentication methods

Authentication Method

Description

Referer Validation

You can configure a referer blacklist and whitelist to identify and filter out malicious visitors.

URL Validation

You can configure a key and validate the URL to protect your livestream resources.

IP Address ACL

You can configure an IP address blacklist and whitelist to identify and filter out malicious visitors.