I have a big problem related to wowzatokenendtime parameter. I want that my HLS streaming url expire after 1 minute to ensure the safety of streaming.
I managed to do this, but SecureToken2 stops the streaming being executed after 1 minute, even if the ClientIP and the SessionID have been accepted. Therefore, it blocks the media .TS
This makes no sense, because the ClientIP and the sessionID are the same. It should block only new connections that trying to use the same url. As it is, I cannot have a URL that expires after 1 minute with videos that have duration of 2 minutes, for example. What the meaning of using the endtime then?
INFO server comment 2015-02-02 10:34:19 - - - - - 580.477 - - - - - - - - [vod/_definst_]ModuleCoreSecurity:current time stamp: 1422880459
The end time parameter is setting the end of validity for the secure token. Since the Secure Token generated is no longer valid after the end time parameter, the streaming session will stop.
What you are suggesting is to have an end time for validating the start of a stream. After the end time has passed, you would like to stop other sessions using the same token to start that stream, but the existing sessions to keep playing back the content using the same token.
Yes, since each of the TS chunks from the Apple HLS stream are requested by the client player, and each request is using the same secure token information, after the end time has passed, that token information is no longer valid so the playback will not continue.
I will make sure to send this use-case to our engineers to take it into consideration for a future Wowza release that would take into account the stream playback validity end time and stream start validity time.
Thanks Zoran. Can you include this in the next release? I need to use this module and it don't have use with this bug.