Reputation: 101
I want to allow video players such as PRESTOplay, Bitmovin, TheoPlayer, ExoPlayer, and Shaka Player to play my own Widevine DRM-protected content.
My Setup: I plan to use Shaka Packager for packaging the content and creating the DASH manifest. I also want to use my own key server instead of relying on other DRM providers. Understanding the Packaging Process: I understand the basics of encrypting content using Shaka Packager. Specifically, I need to provide the signer, aes_signing_key, aes_signing_iv,key_server_url.
Once provided, Shaka Packager generates a response containing:
What I Don't Understand: The Player License Requests Each video player (e.g., Bitmovin, ExoPlayer, Shaka Player) allows specifying a custom license server URL.
When a player requests a license, it sends two requests to the license server. The request payloads are described in this Stack Overflow question (Widevine DRM - Body request payload). My Questions:
0x080x04
.0x080x04
request)?
What should I return in the second response?
What information does this payload contain?
Can I decode it to understand its contents?
How do I integrate the encryption metadata obtained from Shaka Packager into my license server’s responses?Any help, including documentation references, example implementations, or explanations, would be greatly appreciated!
Upvotes: 0
Views: 45