ACTIONSCRIPT 3 Developer’s Guide en

ACTIONSCRIPT 3.0 DEVELOPER’S GUIDE
Using digital rights management
Understanding the protected content workflow
Flash Player 10.1 and later, Adobe AIR 2.0 and later
The following high-level workflow shows that how an application can retrieve and play protected content. The
workflow assumes that the application is designed specifically to play content protected by Flash Access:
1 Get the content metadata.
2 Handle updates to Flash Player, if needed.
3 Check if a license is available locally. If so, load it and go to step 7. If not, go to step 4.
4 Check if authentication is required. If not, you can go to step 7.
5 If authentication is required, get the authentication credentials from the user and pass them to the license server.
6 If domain registration is required, join the domain (AIR 3.0 and higher).
7 Once authentication succeeds, download the license from the server.
8 Play the content.
If an error has not occurred and the user was successfully authorized to view the content, the NetStream object
dispatches a DRMStatusEvent object. The application then begins playback. The DRMStatusEvent object holds the
related voucher information, which identifies the user’s policy and permissions. For example, it holds information
regarding whether the content can be made available offline or when the license expires. The application can use this
data to inform the user of the status of their policy. For example, the application can display the number of remaining
days the user has for viewing the content in a status bar.
If the user is allowed offline access, the voucher is cached, and the encrypted content is downloaded to the user’s
machine. The content is made accessible for the duration defined in the license caching duration. The detail property
in the event contains "DRM.voucherObtained". The application decides where to store the content locally in order
for it to be available offline. You can also preload vouchers using the DRMManager class.
Note: Caching and pre-loading of vouchers is supported in both AIR and Flash Player. However, downloading and storing
encrypted content is supported only in AIR.
It is the application’s responsibility to explicitly handle the error events. These events include cases where the user
inputs valid credentials, but the voucher protecting the encrypted content restricts the access to the content. For
example, an authenticated user cannot access content if the rights have not been paid for. This case can also occur when
two registered members of the same publisher attempt to share content that only one of them has paid for. The
application must inform the user of the error and provide an alternative suggestion. A typical alternative suggestion is
instructions in how to register and pay for viewing rights.
Detailed API workflow
Flash Player 10.1 and later, AIR 2.0 and later
This workflow provides a more detailed view of the protected-content workflow. This workflow describes the specific
APIs used to play content protected by Flash Access.
1 Using a URLLoader object, load the bytes of the protected content’s metadata file. Set this object to a variable, such
as metadata_bytes.
All content controlled by Flash Access has Flash Access metadata. When the content is packaged, this metadata can
be saved as a separate metadata file (.metadata) alongside the content. For more information, see the Flash Access
documentation.
Last updated 6/6/2012
528