Bureaucrats, editor
1,487
edits
Changes
Jump to navigation
Jump to search
Hashcode Editor DRM Protection block allows you to generate a key for content encryption. This key will be inserted in the manifest file and validate (via the DRM Issuer) if the user has access/permission to watch the selected media.
There are some differences between the keys generated for PlayReady and AES and how to generate the key through Hashcode Editor.
<br /><br />
'''PlayReady DRM'''<br />
If the DRM Type field is PlayReady, simply click on the [[File:Regenerate3.png|middle|80px]] button to generate a new set of keys and automatically will generate a set of PlayReady keys that can be used for Live OTT signal encryption:
* Playready Key ID - ID for PlayReady Key.
* PlayReady Content Key Base64 - Key created in 64 bits.
* PlayReady Content Key Hexa - Key created in Hexadecimal.
<br>
[[File:HashCodeEditorPlayReady.png|800px|center|thumb|PlayReady DRM Hashcode editor]]
CDN Lives Page Manual 3.0 (view source)
Revision as of 13:23, 31 October 2022
, 13:23, 31 October 2022→Hashcode Editor
<br />
=== Hashcode Editor DRM Protection ===
----
<br>
The [[File:GenerateButtonGenerateNewKeyButton.pngjpg|middle|70px]] button generates a new hashcodekey, which can be used by other cdn lives that points to it. We have to accept the pop alert, to confirm this action.<br>
<br />
<br>
Alternatively, you can click in the [[File:AddExistingAddExistingKeyButton.pngjpg|middle|80px]] button. A dialog will be open to select an existing set of keys so you can choose the key you want. Take into account that if you link an existing key to this CDN live, it will be unlinked from the previous CDN live.
<br />
<br />
