Stream on-demand encrypted media (pRTMP)

1. Configure protected RTMP for the VOD application.

2. Open fmsrootinstall/applications/vod/Application.xml in a text editor.

3. Add the <ProtectedRTMP enabled="true"></ProtectedRTMP> element. The Application.xml file looks like this:

   <Application> 
       <ProtectedRTMP enabled="true"></ProtectedRTMP> 
       ... 
   </Application>

4. Save and close the file.

5. If the VOD application is running, close it to reload the Application.xml file. If the Flash Media Server Start Screen is open, the VOD application is running. Closing the Start Screen closes the VOD application (unless another client is also connected to the VOD application).

1. Double-click the Flash Media Server Sample Video Player to open it in a browser: fmsrootinstall/samples/videoPlayer/videoplayer.html.

2. Click any link in the /applications/vod/media list. Every file that the VOD application streams uses protected RTMP.

To configure protected RTMP, add a <ProtectedRTMP> section to the Application.xml file at the application level or at the vhost level and set the enabled attribute to "true". The other pRTMP parameters have default values. You can use the default values or set the parameters to new values. The following is a sample <ProtectedRTMP> section:

<Application> 
    <ProtectedRTMP enabled="true"> 
        <CommonKeyFile>phds/common-key.bin</CommonKeyFile> 
        <UpdateInterval>60</UpdateInterval> 
        <SWFVerification enabled="true"> 
            <WhiteListFolder>whitelists</WhiteListFolder> 
        </SWFVerification> 
    </ProtectedRTMP> 
</Application>

Use the following parameters in an Application.xml file to configure protected RTMP:

To configure protected RTMP at the plug-in level, write code in the E_APPSTART event to set the F_APP_PRTMP field to true. The other pRTMP fields have default values. You can use the default values or set the fields to new values. Protected RTMP settings in the Application.xml file are overridden in the Authorization plug-in.

The E_APPSTART event is an application-level event that supports reading all application-level fields, including the following:

The E_APPSTART event supports the following new fields for protected RTMP:

The E_PRTMP_WHITELIST event is an application-level event that FMS calls every n minutes (according to the update interval), enabling you to update the SWF/AIR whitelists through the F_APP_PRTMP_SWF_WHITELIST and F_APP_PRTMP_AIR_WHITELIST fields.

Use the following Server-side ActionScript properties to configure protected RTMP:

These properties are filled in by values retrieved from configuration files during the application.onAppStart() event. You can also set values in this event, as follows:

application.onAppStart = function() 
{ 
    trace  ("----------prtmp on start----------"); 
    trac  e("prtmp " + application.prtmpEnabled); 
    trace("prtmpCommonKeyFile " + application.prtmpCommonKeyFile); 
    trace("prtmpUpdateInterval " + application.prtmpUpdateInterval); 
    trace("prtmpSwfVerification " + application.prtmpSWFVEnabled); 
    trace("prtmpSwfWhitelist "   + application.prtmpSwfWhitelistFolder); 
    trace  ("------------prtmp on start-------  -"); 
    application.prtmpEnabled = false; 
    application.prtmpCommonKeyFile = "TEST  "; 
    application.prtmpUpdateInterval = 12000  ; 
    application.prtmpSWFVEnabled = true; 
    application.prtmpSwfWhitelistFolder = ""; 
}

Trace the new values in the application.onConnect() event:

{ 
    trace("----------prtmp on connect----------"); 
    trace("prtmp " + application.prtmpEnabled); 
    trace("prtmpCommonKeyFile " + application.prtmpCommonKeyFile); 
    trace("prtmpUpdateInterval " + application.prtmpUpdateInterval); 
    trace("prtmpSwfVerification " + application.prtmpSWFVEnabled); 
    trace("prtmpSwfWhitelist " + application.prtmpSwfWhitelistFolder); 
    trace("------------prtmp on connect--------"); 
}

The previous code prints an application.log file similar to the following:

#Version: 1.0 
#Start-Date: 2011-10-19 12:20:41 
#Software: Adobe Flash Media Server 4.5.1 d430 x64 
#Date: 2011-10-19 
#Fields: date time x-pid x-status x-ctx x-comment 
2011-10-19 12:20:41 7832 (s)2641173 ----------prtmp on start---------- - 
2011-10-19 12:20:41 7832 (s)2641173 prtmp true - 
2011-10-19 12:20:41 7832 (s)2641173 prtmpCommonKeyFile c:\Program Files\Adobe\Flash Media Server 4.5\conf\_defaultRoot_\_defaultVHost_\streamtest\phds\common-key.bin - 
2011-10-19 12:20:41 7832 (s)2641173 prtmpUpdateInterval 3600000 - 
2011-10-19 12:20:41 7832 (s)2641173 prtmpSwfVerification false - 
2011-10-19 12:20:41 7832 (s)2641173 prtmpSwfWhitelist c:\Program Files\Adobe\Flash Media Server 4.5\conf\_defaultRoot_\_defaultVHost_\streamtest - 
2011-10-19 12:20:41 7832 (s)2641173 ------------prtmp on start-------- - 
2011-10-19 12:20:41 7832 (s)2641173 ----------prtmp on connect---------- - 
2011-10-19 12:20:41 7832 (s)2641173 prtmp false - 
2011-10-19 12:20:42 7832 (s)2641173 prtmpCommonKeyFile c: \Program Files\Adobe\Flash Media Server 4.5\conf\_defaultRoot_\_defaultVHost_\streamtest\TEST - 
2011-10-19 12:20:42 7832 (s)2641173 prtmpUpdateInterval 12000 - 
2011-10-19 12:20:42 7832 (s)2641173 prtmpSwfVerification true - 
2011-10-19 12:20:42 7832 (s)2641173 prtmpSwfWhitelist c:\Program Files\Adobe\Flash Media Server 4.5\WhiteListFolder - 
2011-10-19 12:20:42 7832 (s)2641173 ------------prtmp on connect-------- -

The pRTMP operations that use the most CPU power are generating the DRM metadata and generating a license. Flash Media Server generates DRM metadata the first time a client requests a media file. The server caches the metadata and reuses it for subsequent request for the same media file.

The media license in the DRM metadata imposes a 24-hour time limit on media playback from the point at which the license was generated. Therefore, the server refreshes the license periodically and generates new DRM metadata with a new time-stamp. Configure the <UpdateInterval> parameter to control how often the server generates DRM metadata. The default value is 60 minutes. To use less CPU power, generate the license less frequently.

Flash Media Server uses shared domain certificates (.cer files) for protected RTMP. The server installs with three shared domain certificates. It uses different certificates for desktop, mobile, and set-top.

In the event of a security breach, Adobe will release a security alert telling you to download new shared domain certificates.

To add a shared domain certificate, copy it to the rootinstall/phds/sd folder.

The following files are installed with Flash Media Server to therootinstall/phds/static folder. Do not replace or modify these files.

anonymous; not use license chaining; 24 hours limited license caching; and binding to the Shared Domain is permitted.