I've been using Wowza on EC2 (devpay) successfully now for several weeks. My app is live streaming via RTMP. I'm using RTMP Auth to authenticate originating encoders which are FMLE or Wirecast. That all works fine. I wanted to add authentication to the Flash client player to help thwart leeches on the playback side. I followed the directions on using secure token with Wowza and JW player 5. I modified the JW 5 source to use the shared token per the instructions, and rebuilt player.swf using the flex tools. I also modified the Application.xml in my 'live' sub-dir of my Wowza conf directory. The stream URL in the invocation of the modified player.swf client was changed to be 'rtmpe://server_ip/live'.
The client never plays the stream and I always get this in the log every time the player polls for the stream:
ERROR session comment 2012-04-03 04:39:09 1927003086 126.96.36.199 - 3639 3543 1.411 - - - -- - - 1927003086 ModuleRTMPAuthenticate.checkSecureToken: Action before response received: kill connection: clientId:1927003086
It seems the player.swf is not authenticating properly with the wowza server. However, I know the changes to RTMPMediaProvider.as and the re-compile of player.swf were done correctly per the instructions. My Application.xml in my 'conf/live' folder on the server has this in it...
<Value>FM,Wirecast</Value> <!--FM, Wirecast-->
I've stop and restarted Wowza after modifying Application.xml to be sure it's been reloaded. I also know I'm loading the right modified player.swf in my client browser. Still I can't get this to work and get that above error in the log.
Any ideas to help my debug? Is it possible the instructions for secure token are not 100% correct for live streams on Wowza-EC2 or the latest JW player source?
Thanks for your help.