Secure streaming with Wowza server Streaming Extensions - Demo 11 / 13
Secure streaming with the the Wowza server
The Wowza Media Server supports secure streaming out-of-the-box. It also has the added benefit over HTTP that you cannot see the requested video URL using commonly used browser debuggers such as Firebug. This example uses the Wowza streaming server together with our secure streaming plugin.
The Secure plugin and Wowza server perform a handshake. This guarantees that only those clients that have access to the secret token are able to stream videos from the Wowza server.
HTML code
A Simple player container where the video file is specified in the href attribute.
<!-- player container-->
<a
href="Extremists.flv"
style="display:block;width:425px;height:300px;"
id="wowza">
<!-- splash image inside the container -->
<img src="/img/home/flow_eye.jpg" alt="Search engine friendly content" />
</a>
Flowplayer configuration
This time we have both the RTMP plugin and the secure streaming plugin. Our own dedicaded Wowza server is configured with the default token that is bundled inside the secure plugin and that is why in this case it is not specified in the configuration.
flowplayer("wowza", "http://releases.flowplayer.org/swf/flowplayer-3.2.7.swf", {
clip: {
// use RTMP streaming
provider: 'rtmp',
// with a secured connection
connectionProvider: 'secure'
},
plugins: {
// setup the RTMP streaming plugin
rtmp: {
url: 'flowplayer.rtmp-3.2.3.swf',
// The net connection URL with HDDN looks like this
netConnectionUrl: 'rtmpe://vod01.netdna.com:1936/play'
},
// setup the secure streaming plugin
secure: {
url: 'flowplayer.securestreaming-3.2.3.swf',
// the token value (shared secret).
// Needs to be escaped because our token has a percent sign in it.
token: escape('#ed%h0#w@1')
}
}
});
You can also supply the token in the configuration, making it visible in the page's source code. For full security you need to compile the token inside the plugin. You can do this yourself or you may purchase one from us.