Is SecureToken support for nDVR?
I have DVR source link format: http://${wowzaIP}:1935/${appName}/${streamName}/playlist.m3u8?DVR
How to enable SecureToken for the above link.
I try to generate hash for VOD: vod/sample.mp4?192.168.1.2&mySharedSecret, and it work
But when I try with DVR, it return 403 (Forbidden): live/sample.mp4?192.168.1.2&mySharedSecret
nDVR works with SecureToken, yes.
The user name and password authentication would need to be done through a webpage portal that has a player hosted with the stream from Wowza.
The users would login using the webpage, then the page with the player would be loaded to playback the HLS DVR stream.
I don’t believe there are any HLS players that would work with an HLS user name and password authentication like you are referencing.
Send us a support ticket @chi_nk1 and we’ll take a closer look and help you get it set up.
I follow this below link to setup SecureToken .
https://www.wowza.com/docs/How-to-protect-streaming-using-SecureToken-in-Wowza-Streaming-Engine
Use Wowza SecureToken to protect streams
Wowza Streaming Engine™ media server software provides SecureToken playback protection for all supported streaming protocols and includes hashing options for generating the security token that’s exchanged between Wowza Streaming Engine and its clients.
It has HLS instructions for VOD but no HLS for nDVR.
With VOD, String used for hashing vod/sample.mp4?192.168.1.2&mySharedSecret&myTokenPrefixCustomParameter=abcdef&myTokenPrefixendtime=15000 00000&myTokenPrefixstarttime=1395230400
With nDVR, I try to used live/sample.mp4?192.168.1.2&mySharedSecret&myTokenPrefixCustomParameter=abcdef&myTokenPrefixendtime=15000 00000&myTokenPrefixstarttime=1395230400. But it not work
I want to comfirm that, protect streaming using SecureToken in Wowza Streaming Engine is worked for nDVR, and what is the string using for hash.
And about “The users would login using the webpage, then the page with the player would be loaded to playback the HLS DVR stream.”. This way is work. But I want to use SecureToken in this case.