Adobe® Flash® Access™ 3.0 SDK
Copyright 2011 Adobe Systems Incorporated. All rights reserved.
This file contains important information that was not available when the product documentation was written. Review this information before running this version of the Adobe Flash Access SDK.
Flash Access Client Known Issues
Note: Flash Access Client Release Notes – unless stated otherwise, issues apply to both Flash Player and AIR on desktop (PC, Mac, Linux) and mobile clients. Also, please refer to the release notes for Flash Player 11 and AIR 3.
When streaming content with only the audio track encrypted over Protected HTTP Dynamic Streaming, playback of the stream will not automatically begin when using OSMF.
As a work-around in a video player, expand the logic for the “play” button with the following ActionScript: player.play(); player.stop(); player.play().
On Android devices, the Flash Access client returns 3315 (Security Context) for the error code, when the error code should be 3305 (Cannot Connect To Server).
Based on logic flow context, the video player should consider this error code and recognize there is an issue preventing the client connecting to the license server.
On Android devices, a 3328 (Server Error) error is returned when a 3329 (Application-Specific Namespace Error) should be.
Based on logic flow context, the video player should consider this error code and recognize that the source of this issue is a an error returned by the license server. Custom codes returned by the server, typically available through a sub-error code with 3329 errors, will not be visible to applications running on Android devices.
On Android devices, if there are file permission issues and the device is unable to persist Flash Access licenses to disk, a 3307 (System Error) will be thrown, instead of the expected 3313 (Write Microsafe Failed).
When attempting to write a license to the local secure store, the video player should also expect the 3307 (System Error) error code.
On Android devices, clearing the browser data will wipe out all Flash Access licenses acquired through the web browser.
This happens ONLY when clearing the application data for the browser itself, clearing the browser cache does NOT clear the stores. Also, this does NOT affect licenses acquired through an AIR application.
Flash Media Rights Management Server (FMRMS) 1.5 AIR applications running on Mac will not be able to play encrypted video after calling the DRMManager.resetVouchers() API (the client application will get a 3313 error, Write Microsafe Failed).
The work-around for this problem is to have the FMRMS 1.5 AIR application restarted after using the DRMManager.resetVouchers() API.
SystemUpdater.update("DRM") will fail if the client's system clock is rolled back far enough (for example, 1 year).
When a user sets the client system clock back a very long time (e.g., one year), the Flash Access client will throw a 2203 error (Generic Error). In the absence of this error, the Flash Access clock rollback detection prevents attacks on the playback window.
Authentication property in the DRMStatusEvent in AIR when using multiple policies
When embedding multiple policies in a single piece of content, the authentication property in the DRMStatusEvent is not displayed correctly in AIR.
On Ubuntu 10.10 or higher, a 2203 (SystemUpdater Error), 3322 (Device Binding Failed), or 3323 (Internal Stores Corrupted) is thrown.
Ensure that the “hal” and “libhal1” libraries are installed and running. To install these libraries, run:
sudo apt-get install libhal1
sudo apt-get install hal
Flash Access Server SDK Known Issues
LunaSA HSM certificate corruption (Third party issue)
For LunaSA HSM devices, when re-importing X509Certificates into the appliance, you must first delete the one previously there. Not doing so will corrupt the HSM's handle to the cert. The cert will export to file cleanly, but internally becomes corrupt, leading to JCA based retrieval errors.
Domain name when using white-lists for Adobe® Flash® Player SWFs
When using a URL for the Flash Player white-list the domain name must be in all lowercase characters.
List of policies in the Flash Access Manager does not display correctly a second time
If you click on the Policies drop-down in the Flash Access Manager a second time, it incorrectly shows the details of the policy in the drop-down list. To refresh this list de-focus the FlashAccessManager window by clicking on another application and then click on the FlashAccessManager window again. The drop down will then display the list of existing policies correctly.
On Windows, the Reference Implementation Command Line Tools do not interpret dates correctly when "(GMT)Greenwich Mean Time" time zone is used. (Third party issue)
The "(GMT)Greenwich Mean Time" time zone on Windows may not map to the proper time zone in Java. If dates specified in the Reference Implementation Command Line Tools do not interpret dates correctly, set the Java time zone using the “user.timezone” Java System property.
When using the packaging feature to leave the initial portion of the content in the clear, you must enable encryption for audio and video tracks.
The source for building the Flash Player and AIR Sample Video Players using Adobe Flash Builder 4 is located on the Flash Access DVD in “Reference Implementation/Sample Video Players/Flash Player/Source” and “Reference Implementation/Sample Video Players/AIR/Source” respectively.
To build the player, you may use Flex SDK 4.1 that comes with Flash Builder 4, or use the latest Flex SDK 4.5. The later enables the use of the Stage Video. Flex SDK 4.5 can be downloaded from here: http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+4.5
This Sample Video Player is built upon OSMF (Open Source Media Framework). Find the OSMF.swc in “Reference Implementation/Sample Video Players/Flash Player/OSMF” and “Reference Implementation/Sample Video Players/AIR/OSMF”, respectively.
Following are steps to import the sample video player into Flash Builder IDE. The “<SDK>” you will see in the instructions below represents the Flex SDK you choose to compile the source file.
This section identifies how to build Flash Access-based AIR apps using the respective platforms for development.
For this version of Flash Access the documentation is available at http://www.adobe.com/go/learn_flashaccess_documentation_3
Additional Licenses and Copyrights
By installing this product, in addition to the Adobe license terms, you may also be subject to certain the third-party terms that are specified in the product documentation at www.adobe.com/go/thirdparty or in the folder labeled “third_party” included with the software. Adobe recommends that you review these third-party terms.