Archived:How to protect Flash Lite content with OMA DRM 1.0
I will use the NMIT 4.1 tool to apply Forward Lock DRM to a Flash Lite file with a step by step process. I will not go into details for each option but you can refer to the NMIT 4.1 User Guide to learn more about all the capabilities and features of the tool.
Step 1 (see Figure 1)
Figure 1. Nokia Mobile Internet Toolkit 4.1 start-up screen
Step 2 (see Figure 2)
1. Select File > New. The Available Content Types screen will open 2. Select the Deployment tab 3. Select the DRM Message icon 4. Press OK
Figure 2. NMIT 4.1 – Deployment screen
Step 3 (see Figure 3)
Figure 3 shows a screen where I will define the type of DRM to apply to the Flash Lite content. There are four sections on this screen.
The first section, "1. Select Message Type" allows you to select which type of OMA DRM 1.0 to apply to the content. I use Forward Lock so no changes are needed since this is the default.
The second section, "2. Load Media Content", allows you to load the file that you want to protect. In my case it is a Flash Lite file (SWF). Also leave the "Content-Transfer-Encoding" set to binary.
The third section, "3. Edit Header", allows you to define the headers. Since Flash Lite content is now automatically recognized by the tool, I will enter the application/x-shockwave-flash information into the Content-Type line.
The fourth section, "4. Specify Rights" is not used for Forward Lock DRM. In case you use another DRM protection method, you will have several options available. Refer to the tool manual for more information.
Figure 3. DRM definition window.
Step 4 (see Figure 4)
1. Load your Flash Lite file using the "Load Content" button from the section "2. Load Media Content". I loaded the testdrm.swf. You can find this file in the Sample files linked from the beginning of this article. 2. Add the application/x-shockwave-flash information into the Content-Type line in the "3. Edit Headers" section. This step is necessary since the tool does not recognize the Flash file format. 3. Make sure to click on the Binary field. The tool seems to have a bug which does not apply the application/x-shockwave-flash MIME until the second field is selected. 4. Save the file. I saved as testdrm.dm.
At this point I have a so-called DRM message file ready for deployment. I will need to upload it to my web server for download and installation.
Figure 4. Apply OMA DRM 1.0 Forward Lock to the testdrm.swf
Important Note: The protection will only be applied once you download the .dm file from the mobile site to your phone. This is only one of the delivery methods used by OMA DRM. For other delivery methods please consult the documentation.
Testing OMA DRM 1.0 Forward Lock Flash Lite protected content
I created a simple mobile web page with a link to the testdrm.dm file. You can use Adobe Dreamweaver CS3 to create a mobile web page. Here is a step by step process:
1. Upload the files, index.html and testdrm.dm to your web server. 2. Browse to the mobile web page using the browser of your mobile phone. 3. Select the link to the testdrm.dm file, Figure 5.
Figure 5. Select testdrm.dm
4. Select the location where you want to save the file (see Figure 6).
Figure 6. Select location
5. At this point the download of the file starts (see Figure 7).
Figure 7. Downloaded testdrm.dm
6. Save the file to the phone (see Figure 8).
Figure 8. testdrm.dcf saved
7. On the phone go to the location where the file was saved. On Nokia S60 devices, this is usually the Other directory. You can just select the Flash Lite player icon and you will see the testdrm.dcf file (see Figure 9).
Figure 9. testdrm.dcf in the Flash Lite
The yellow key icon indicates that the file is DRM protected.
You can now execute the Flash Lite content (see Figure 10).
Figure 10. Test testdrm.dm on the phone
To test that the file is protected with Forward Lock DRM, try to send the file via MMS or Bluetooth to another handsets (see Figure 11).
Figure 11. Send the file to another handset
You will see the following message "unable to send protected object" (see Figure 12).
Figure 12. The "unable to send protected object" message
If you do not have a Web Server to test this process you can just point your mobile browser to the following URL:
Or if you have a mobile phone with a 2D bar code reader just scan the following bar code:
Figure 13. Bar code generated with Nokia Mobile Code.