ACTIONSCRIPT 3 Developer’s Guide en

ACTIONSCRIPT 3.0 DEVELOPER’S GUIDE
Using digital rights management
Out-of-band Licenses
Flash Player 11 and later, Adobe AIR 3.0 and later
Licenses can also be obtained out-of-band (without contacting a Flash Access License Server) by storing the voucher
(license) on disk and in memory using the storeVoucher method.
To play encrypted videos in Flash Player and AIR, the respective runtime needs to obtain the DRM voucher for that
video. The DRM voucher contains the video’s decryption key and is generated by the Flash Access License Server that
the customer has deployed.
The Flash Player/AIR runtime generally obtains this voucher by sending a voucher request to the Flash Access License
Server indicated in the video’s DRM metadata (DRMContentData class). The Flash/AIR application can trigger this
license request by calling the DRMManager.loadVoucher()method. Or, the Flash Player/AIR runtime will
automatically request a license at the start of the encrypted video playback if there is no license for the content on disk
or in memory. In either case, the Flash/AIR application’s performance gets impacted by communicating with the Flash
Access License Server.
DRMManager.storeVoucher() allows the Flash/AIR application to send DRM vouchers that it has obtained out-ofband
to the Flash Player/AIR runtime. The runtime can then skip the license request process and use the forwarded
vouchers for playing encrypted videos. The DRM voucher still needs to be generated by the Flash Access License Server
before it can be obtained out-of-band. However, you have the option of hosting the vouchers on any HTTP server,
instead of a public-facing Flash Access license server.
DRMManager.storeVoucher() is also used to support DRM voucher sharing between multiple devices. In Flash
Access 3.0, this feature is referred to as “Domain Support”. If your deployment supports this use case, you can register
multiple machines to a device group using the DRMManager.addToDeviceGroup() method. If there is a machine with
a valid domain-bound voucher for a given content, the AIR application can then extract the serialized DRM vouchers
using the DRMVoucher.toByteArray() method and on your other machines you can import the vouchers using the
DRMManager.storeVoucher()method.
Device registration
The DRM vouchers are bound to the end user’s machine. Hence Flash /AIR applications will need a unique ID for the
user’s machine to refer to the right serialized DRM voucher object. The following scenario depicts a device registration
process:
Assuming that you have performed the following tasks:
You have set up the Flash Access Server SDK.
You have set up an HTTP server for obtaining pre-generated licenses.
You have created a Flash application to view the protected content.
The device registration phase involves the following actions:
1 The Flash application creates a randomly generated ID.
2 The Flash application invokes the DRMManager.authenticate() method. The application must include the
randomly generated ID in the authentication request. For instance, include the ID in the username field.
3 The action mentioned in Step 2 will result in Flash Access sending an authentication request to the customer’s
server. This request includes the device certificate.
a The server extracts the device certificate and the generated ID from the request and stores.
Last updated 6/6/2012
544