Hello,
I’ve setup the Wowza Player, all seems to work fine, also using the Secure Token mechanism (V2 / SHA). Only for the flash fallback this fails. I couldn’t find this in the documentation and I am wondering what the way this should be implemented. (Since the TEA shared key normally needs to be compiled within the Flash player.)
Is there also a parameter to force disabling flash? (I tried setting “useFlash” to false.)
Thank you in advance.
Best regards, Joost
Hello Joost,
There have been quite a few updates to our Wowza Player since your post, and I wanted to check in and see if you are still seeing this issue?
If you are still seeing this issue, can you log a support ticket here:
https://www.wowza.com/support/open-ticket
Regards,
Jason Hatchett
@Jason Hatchett I am seeing a similar issue with SecureToken on the flash fallback in the Wowza Player. The sourceURL contains the required query string params for secureToken (hash, starttime, endtime). However, the flashvars for the flash player contain the Wowza Player configuration variables, including the sourceURL, where each variable is separated by ‘&’. This is causing the flash player to read the sourceURL up to the first SecureToken param, and the subsequent params are interpreted as separate flashvars. The request for the sourceURL is rejected because it doesn’t contain all the SecureToken required params.
I am able to get the flash player working if I disable the Playback Security, and I am able to get the HTML5 player working with Playback Security enabled.
Thank you for any help you can provide.
i have the same problem with strobe flash player in combination with secure token.
are there any solutions?