erankor
commented
8 years ago The encryptionKey field is indeed only used to decrypt previously encrypted MP4 files. It should be possible to accomplish what you need with the latest changes that were added to support FairPlay. You need to enable DRM on the HLS location (vod_drm_enabled on), and use vod_drm_upstream_location & vod_drm_request_uri to configure how nginx-vod-module should access the key server. The key server should return a JSON in this format:
[{
"key": "AAAAAAAAAAAAAAAAAAAAAA==",
"key_id": "BBBBBBBBBBBBBBBBBBBBBB==",
"iv": "CCCCCCCCCCCCCCCCCCCCCC=="
}]All fields are 128 bit base64-encoded. key_id is not relevant for HLS, but the module requires it since it's needed in other protocols. The IV is optional. Other than that, you will need to set vod_hls_encryption_key_uri to some URL (can contain nginx variables) since in DRM mode nginx-vod-module does not return the encryption key to the client
xXxSPYxXx
Ivars
jessp01
Hello,
Is it somehow possible to configure HLS encryption key parameter so Nginx server would request and acquire the encryption key from some other server?
What I want to achieve is the following scenario:
Module's documentation mentions encryptionKey parameter in Mapping reference: https://github.com/kaltura/nginx-vod-module#source-clip
encryptionKey - a base64 encoded string containing the key (128 bit) that should be used to decrypt the media file.
Is it possible to use this encryptionKey in my scenario or is it used to serve key to decrypt video which is already encrypted with this key?