Update your Adaptive Media Delivery property
In order to apply the Instant TV and Live2VOD features, you need to change a few settings in your Adaptive Media
Delivery property configuration.
- In Property Manager, set the match criteria to match on archive manifest file extensions .m3u8 or .mpd with properly formatted Query String Parameters in the request URLs.
This example also shows endTime
, but that's optional.
- Add a Cache Key Query Parameters behavior to include
startTime
as an exact match (endTime
is
optional). - Add a Caching behavior to Force revalidation of stale objects with origin.
- If you're using token authentication with Instant TV, you need to need to enable Token in URI and add
{filename}-archive.m3u8
in the Master Manifest Files list.
You can also include a Filename match criteria to match on
-archive
. This prevents requests for other manifest files that includestartTime
andendTime
as query string parameters from being interpreted as Instant TV requests. This example also shows
- Configure G2O Authentication in Akamai AMD
After the G2O configuration is applied on the MSL Origin side, the corresponding G2O setting—specifically the addition of theX-Akamai-G2O-Auth-Data and X-Akamai-G2O-Auth-Sign
headers—needs to be configured on the CDN side.
For the Akamai CDN, follow these steps in the Akamai AMD UI. There are two possible workflows for G2O
authentications in AMD:
- Akamai Signature Header Authentication
- Signature Header Authentication
Akamai Signature Header Authentication
- Navigate to Origin Characteristics.
- Set the Authentication Method to "Akamai Signature Header Authentication".
- Encrypted Algorithm Version: SHA256-HMAC
- Signed String Type: Default (Forward URL)
- Secret Key: Match this with the "Key" value configured in the MSL5 Origin shared key.
- Nonce: Match this with the "Name" value configured in the MSL5 Origin shared key.
Signature Header Authentication is required when configuring AMD with the old rule format. If your AMD uses the old rule format, the above "Akamai Signature Header Authentication" is unavailable for selection.Signature Header Authentication]
This configuration is not needed if you have already configured "Akamai Signature Header
Authentication".
- Navigate to the Signature Header Authentication section.
- Clear Data Header Name: X-Akamai-G2O-Auth-Data
- Encrypted Data Header Name: X-Akamai-G2O-Auth-Sign
- Encrypted Algorithm Version: SHA256-HMAC
- Signed String Type: Default (Forward URL)
- Secret Key: Match this with the "Key" value configured in the MSL5 Origin shared key.
- Nonce: Match this with the "Name" value configured in the MSL5 Origin shared key.
- In addition to the above configuration on "Signature Header Authentication", configure the following Origin
Server settings:
- Origin Type: Refer to "Your Origin".
- Forward Host Header: Refer to the "Origin Hostname".
Updated about 8 hours ago