DRM License Generator
Use AdobeLicenseGenerator.jar to generate licenses without requiring the client to send a license request to a server. You can then embed a pre-generated license in the content, or deliver the license to the client through other mechanisms, such as a simple HTTP web server.
License Generator command-line usage
Generate a license:
java -jar AdobeLicenseGenerator.jar -m <i class="+ topic ph hi-d="" i "=""> metadata <i class="+ topic ph hi-d="" i "=""> [options] </i class="+ topic> </i class="+ topic>
- metadata - Includes the Adobe Primetime DRM metadata.You can retrieve this file from protected content with the -d -m options in the Media Packager.
Display a previously generated license:
java -jar AdobeLicenseGenerator.jar -d <i class="+ topic ph hi-d="" i "=""> license </i class="+ topic>
- license - Contains a Adobe Primetime DRM license generated by the License Generator.
Table 6: Options
Command Line Option
Specifies the name and location of the configuration file.
If you do not specify a name or a location, the DRM License Generator searches for flashaccesstools.properties in the current working directory.
Note: Options that you specify on the command line take precedence over the options you specify in the configuration file.
|Displays information about a license that has already been generated.|
|-leaf leaf-filename||Generates a leaf license and saves the output in a specified file.|
|-m metadata-filename||Specifies the content metadata for which you need to generate a license. This option is required to generate a license.|
|-noprompt||Do not ask if the destination file should be overwritten. If the destination file already exists and the -o has not been set, an error occurs.|
|-o||If the destination file already exists, you can overwrite it without being prompted.|
If the metadata includes multiple DRM policies, you can specify the number of DRM policies that you can use to generate a license.
If you do not specify the number of DRM policies, the first DRM policy is automatically applied.
|-r recipient-cert||Generates a license for a specified recipient. You can use a device or domain certificate, and you can specify multiple -r options to create a license for multiple recipients.|
|-root root-filename||Generates a root license and saves the output to a file that you specify.|
Configuration file properties
Before running the License Generator, you need to specify values for the License Generator properties in the configuration file.
For property names that include n , n represents an integer that starts with 1 and increases for each instance of the property.
Sets the currently supported minimum client version. If you do not set this property, all versions are automatically supported by default.
You can set this value to control how older clients respond to the license requirements that they do not support. Specify x (for Adobe Primetime DRM x.0) where x represents a major release number.
|licensegen.keyServerCert||Key Server Certificate, which is an Adobe-issued License Server certificate that is used by the Key Server. This certificate is applied only if the metadata/DRM policy indicates that a Key Server is required for key delivery to iOS devices.|
|licensegen.sign.certfile||The PKCS12 file that includes the License Server credentials for signing licenses. This property needs to refer to a .pfx file that includes a certificate and private key.|
|licensegen.sign.certpass||The password that protects the file that you have specified with the licensegen.sign.certfile option.|
If you generate domain-bound licenses, you must specify one or more Domain CA certificates to indicate the domain authorities that the license issuer can trust.
If the license recipient is a domain certificate, which was not issued by one of the specified Domain CAs, then a license cannot be generated. This property specifies a .cer file that includes the certificate in the PEM or the DER format. n must increase monotonically, starting from 1.
Optional PKCS12 file that includes additional License Server credentials for decrypting the CEK in the metadata and DRM policy. You can configure additional credentials if content has previously been packaged with a License Server certificate other than those credential that have been specified with licensegen.sign.certfile . This property needs to refer to a .pfx file that includes a certificate and private key. n must increase monotonically, starting from 1.
The password is applied to protect the file that you have specified with the licensegen.keys.asymmetric.licenseServerCredential.n property.