License Server SDK Overview
What the SDK is, where it sits, request/response cycle.
Where the SDK fits
The License Server SDK is a server-side library that takes:
- An opaque licence-request blob from the CDM (sent via the application).
- A policy you construct (durations, persistence, HDCP requirements, etc.).
- The relevant content keys (looked up by KID).
…and returns an opaque licence-response blob. The application sends that response back to the CDM. The SDK does not authenticate users, look up entitlements, or talk to your database. That's the integrator's responsibility on top.
Conceptual request flow
Application — Receives POSTed request blob + auth header
From the player. Auth header contains a signed application token tying user / content / device tier.
What this module covers vs in-class
The exact API surface, type names, and authentication model of the SDK come from the in-person training material under NDA. This page captures the public-facing concepts you'll need to recognise on the exam. Use the internal.mdx pattern (gitignored) to record class-specific details.
After Day 2 of the in-person training, return here and create internal.mdx in this folder with the API names, request/response struct names, and the policy builder details from the lab.