Glad to hear the content works for you. Here are some test cases you can use in the future, if you would like to demo the Output Protection feature of Flash Access. Before going into the test cases, I'd like to note one thing - that all laptop displays are identified as "internal/embedded displays", and content which is protected with Output Protection will always play on laptops or embedded devices. Output Protection restrictions only come into play when you hook up an external monitor.

[ If you are using the Reference Implementation License Server ]

1. Package content, ensuring the following properties are set in your flashaccesstools.properties file when creating the policy:

1a. policy.outputProtection.analog=REQUIRED

1b. policy.outputProtection.digital=REQUIRED

2. Play the content on a Windows or Mac laptop; notice the video plays.

3. On the Windows machine, attach a monitor that is HDCP compliant & play the same video; notice the video plays.

4. On the Mac machine, attach a monitor that is HDCP compliant & play the same video; notice the video does NOT play.

5. On the Windows machine, attach a monitor that is not HDCP compliant; the video should not play.

2. Follow the same test cases mentioned above. Note that there is no need to explicitly specify rights/restrictions in the policy, as the License Server for Protected Streaming will ignore whatever is specified in the content's policy and only apply the rights/restrictions listed in the flashaccess-tenant.xml file.

For each of the 4 samples, could you summarize what DRM feature each implements? And what minimum version of Flash Player will be required for playback of each? Lastly, if possible including links into the documentation regarding what DRM feature each implements?

I ask about Flash Player versions because I assume some may require FP 10.1? Or FP 10.0? Yet others earlier versions of FP? For instance, can any use FP 9 or earlier?

Thank you again for the great resource that these sample links are. (Plus, I love the various personas of Karl Miller that they demonstrate ;-)

1. All Flash Access enabled content require Flash Player 10.1 or later. Flash Player 10 and before has no support for Flash Access.

As for descriptions of the 4 DRM sample content provided by Adobe, all functionality provided by our policy and packaging tools (as well as the SDK they use) can be found in the "Protecting Content" document. I'll list page numbers for how to set these particular properties using our Java-based AdobePolicyManager.jar tool. The nice thing about knowing the property names the tool uses is that they correlate with the Flash Access Java API class of what you'll have to modify, if using the SDK directly. For instance "policy.startDate" correlates to the Java API "com.adobe.flashaccess.sdk.policy.Policy.getStartDate()".

Flash Access 2.0 provides the ability to specify whether an output to external rendering devices is protected. You can specify analog and digital outputs independently. For more information, you can look at our documentation and go to the subsection on Output Protection: http://help.adobe.com/en_US/flashaccess/2.0/protecting_content.pdf

3. The "authentication dialog" for Strobe comes into play if you encrypt a piece of content and designate that it requires authentication. By doing this, you are using Flash Access' authentication mechanism. When setting up your Flash Access license server, you should install the Reference Implementation license server, which supports Flash Access authentication out-of-the-box, and has SQL scripts to add some sample users.

But the thing is i am bit confused with the strobe media playback source code.

That is beacuase i donot know much about ActionScript 3.0, but side by side i am also learning as3.

Please suggest how i will be able to understand the flow and edit available feature like changing default position of control bar elements, adding logo image to video being displayed in strobe media playback and other things.

If your goal is to protect the content, then simply using Flash Access will assure that.

Users will always be able to save content that is streamed to their computer; there are several ways to do this. However, if the video is protected by Flash Access, it is encrypted in such a way that only the client that was issued the license can playback the video. In addition, the license issued by Flash Access is bound to the client that requested it - it cannot be copied to other computers.

This binding of licenses to the client, encryption, and license rights and restrictions provided by Flash Access, provides the highest level of security for your video content.

Unfortunately, http://drmtest.adobe.com is temporarily down for maintenance. I am unsure when our IT team will be able to bring the machine back online.

In the meantime, though, another option to validate Flash Access has installed correctly would be to visit one of our customer's site, who has deployed Flash Access, like www.vudu.com. Playback of any of their videos will indicate the successful installation of Flash Access.