ACTIONSCRIPT 3 Developer’s Guide en

ACTIONSCRIPT 3.0 DEVELOPER’S GUIDE
Using digital rights management
3 Get the voucher for the content by performing one of the following tasks:
a Use the DRMManager.loadVoucher() method.
b Obtain the voucher from a different device registered in the same device group. Provide the voucher to the
DRMManager through the DRMManager.storeVoucher() method.
4 Play the encrypted content using the NetStream.play() method.
To export the license for the content, any of the devices can provide the license’s raw bytes using the
DRMVoucher.toByteArray() method after obtaining the license from the Flash Access License Server. Content
providers typically limit the number of devices in a device group. If the limit is reached, you may need to call the
DRMManager.removeFromDeviceGroup() method on an unused device before registering the current device.
License preview
The Flash application can send a license preview request, meaning that the application can carry out a preview
operation before asking the user to buy the content in order to determine whether the user’s machine actually meets
all the criteria required for playback. License preview refers to the client's ability to preview the license (to see what
rights the license allows) as opposed to previewing the content (viewing a small portion of the content before deciding
to buy). Some of the parameters that are unique to each machine are: outputs available and their protection status, the
runtime/DRM version available, and the DRM client security level. The license preview mode allows the
runtime/DRM client to test the license server business logic and provide information back to the user so he can make
an informed decision. Thus the client can see what a valid license looks like but would not actually receive the key to
decrypt the content. Support for license preview is optional, and only necessary if you implement a custom application
that uses this functionality.
Delivering content
Flash Access is agnostic to the delivery mechanism of the content as the Flash Player abstracts out the networking layer
and simply provides the protected content to the Flash Access subsystem. Hence, content can be delivered through
HTTP, HTTP Dynamic Streaming, RTMP, or RTMPE.
However, you may get some issues due to the necessity of the protected content’s metadata (usually in the form of a
‘.metadata’ file) before Flash Access can acquire a license to decrypt the content. Specifically, with the RTMP/RTMPE
protocol, only FLV and F4V data can be delivered to the client through the Flash Media Server (FMS). Because of this,
the client must retrieve the metadata blob by other ways. One option to solve this problem is to host the metadata on
an HTTP web server, and implement the client video player to retrieve the appropriate metadata, depending on the
content being played back.
Last updated 6/6/2012
546