Migrating to a Different License Server
.gif)
| Previous | Next |
Migrating to a Different License Server
If you decide to migrate from one license server to another (for example, to change license providers), you must provide the following information to the new license provider to support your existing content and to continue issuing licenses for it.
Note Because all of these values are used to decrypt content, they should be shared in a secure manner.
License key seed and content keys
A license key seed and key ID are used to generate the content key that encrypts and decrypts content. Therefore, the license provider needs this license key seed to generate the content key for the license.
Important Take care not to lose your license key seed because once lost, there is no way to recover it.
If your license acquisition process stores keys in a database during content protection, and then retrieves keys rather than regenerates them for each license request, you should also provide all of the content keys for your content.
For more information about the license key seed, see Creating Packaged Windows Media Files. For more information about content keys, see Generating Key IDs, Keys, and Content IDs.
Public signing key
A public-private key pair is used for signing the content header. The private key is used to sign the content header while protecting the content, and the public key is used to verify that signature while generating a license. Therefore, you must provide this public signing key to the new license provider.
For more information about the signing key pair, see Creating the Content Header.
License acquisition URL
The license acquisition URL is included in protected content and indicates where its license is issued. The license acquisition URL in existing content points to the old license server. Provide this URL to the new license provider so that they can redirect users to the new license acquisition page.
For more information about license acquisition URLs, see Creating the Content Header.
Public-private keys for license revocation
If the previous license provider supported license revocation, a license revocation public-private key pair was used for this process. The public key was included in licenses as the value of the LGPUBKEY attribute, and then the private key could be used by the license server to revoke licenses. This license revocation key pair should be shared with the new license provider.
For more information, see Implementing License Revocation.
Metering certificate, URL, and key pair
If you support metering for your content, the metering certificate must be shared with the new license provider for inclusion in new licenses.
If the previous license provider also acted as the metering aggregation service, and if the new license provider will assume this role, the new license provider needs the public-private key pair that is used with the metering certificate, and the metering URL of the metering aggregation service so that it can be redirected.
For more information, see Hosting a Metering Aggregation Service.
See Also
| Previous | Next |