|
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 Adobe 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:
-
The Flash application creates a randomly generated ID.
-
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.
-
The action mentioned in Step 2 will result in Adobe Access
sending an authentication request to the customer’s server. This
request includes the device certificate.
-
The server
extracts the device certificate and the generated ID from the request
and stores.
-
The customer sub-system pre-generates licenses for this device
certificate, stores them and grants access to them in a way that
associates them with the generated ID.
-
The server responds to the request with a “success” message.
-
The Flash application stores the generated ID locally in
a Local Shared Object (LSO).
After the device registration, the Flash application uses the
generated ID in the same way as it would have used the device ID
in the previous scheme:
-
The Flash application will try to locate the generated
ID in LSO.
-
If the generated ID is found, the Flash application will
use the generated ID while downloading the pre-generated licenses.
The Flash application will send the licenses to the Adobe Access
client for consumption using the
DRMManager.storeVoucher()
method.
-
If the generated ID is not found, the Flash application will
go through the device registration procedure.
|
|
|
