Updating On-board Setup
Even if you run Axinom DRM on-board in a disconnected environment, you still have to update certain components periodically after initial installation.
This article describes the updates to the tenant configuration.
For the device lists see Widevine Device Certificate Status List and PlayReady Revocation List.
There are different ways to perform the updates:
Manual Updates​
If you have a direct access to the host running Axinom DRM, you can simply store the new files in the Config folder.
The License Service will reload the new configuration in one of the three ways:
- After a container restart
- Automatically, per default every 5 minutes (configurable using
FrontendDataUpdateInterval) - Ad-hoc, after a
POST /Sync/Now(see the authorization details of the Sync API below).
Push-Updates using Sync API​
If you regularly update the DRM configuration without manually logging in to the server, you may have some agent running in the same on-board environment where the DRM License Service runs. This agent can talk to the Sync API of the License Service to automatically push the new configuration.
The Sync API provides the following endpoints (all accessible via POST):
| Endpoint | Purpose | Request type |
|---|---|---|
| /Sync/Now | Reloads all configuration files | |
| /Sync/Tenants | JSON | |
| /Sync/KeySeeds | JSON | |
| /Sync/CommunicationKeys | JSON | |
| /Sync/FairPlayDataSets | JSON | |
| /Sync/DeviceCertificateStatusList | See Device Certificate Status List | JSON |
| /Sync/RevocationList | See Revocation List | XML |
The body of each request is the same as of the respective .json/.xml configuration file.
For all requests (except /Sync/RevocationList, which uses application/xml content type) set the following HTTP header:
Content-Type: application/json; charset=utf-8
To be able to use the Sync API please use the API key. You can set the desired API key in the ApiKeys.json file in the Config folder. Add the following HTTP header:
Authorization: Basic base64(:$apiKey)
You can use the base64 tool to transform a string to base64.
Disabling Automatic Reload​
Per default the License Service reloads the configuration files every 5 minutes.
If you decide to restart the container manually when you update the files or to use the Sync API to push the updates, you should disable automatic reloading, as you know the files will not change in between.
To disable automatic reloading set the FrontendDataUpdateInterval to 0 in the Application Configuration.