DRM-X 6.0Canvas, Blackboard, Brightspace and Open edX
Use the LTI 1.3 bridge to open protected video from an LMS with a signed platform launch.
Comment la lecture est autorisée
Votre backend décide qui peut regarder le contenu. DRM-X fournit l’autorisation de lecture. Le lecteur l’utilise pour demander une licence DRM.
- Spectateur
Se connecte à votre service et demande une vidéo.
- Votre backend
Vérifie l’achat, l’abonnement ou toute autre autorisation d’accès de l’utilisateur.
- DRM-X
Applique les règles choisies et renvoie la configuration ainsi que l’autorisation de lecture.
- Lecteur
Utilise l’autorisation reçue pour demander la licence DRM nécessaire à la lecture.
Deploy the LTI bridge#
Run the Node.js 24 bridge behind an HTTPS reverse proxy. Store the configuration and SQLite state database outside the public web directory. Set DRMX_BRIDGE_CONFIG, DRMX_BRIDGE_DATABASE, DRMX_SITE_ID, DRMX_SITE_KEY and DRMX_ACCESS_KEY in the host environment.
The current bridge implements LTI 1.3 Resource Link launches. It does not implement grade passback, roster synchronization or Deep Linking selection. Add each resource link in the LMS and map its signed resource-link ID in the server configuration.
Register the tool#
Register the OIDC login URL as https://YOUR-TOOL/lti/login and the launch/redirect URL as https://YOUR-TOOL/lti/launch. Copy the LMS issuer, client ID, deployment ID, authorization URL and public JWKS URL into config.example.json. Do not accept these values from an unregistered launch.
Canvas: create an LTI developer key, enable it, and install the tool by client ID at the intended account or course. Blackboard Learn: register an LTI 1.3 provider and placement, then copy the deployment details. Brightspace: register the tool, deploy it to the intended organizational units, and create a link.
Open edX: enable and configure the LTI Consumer component for LTI 1.3, then add the external tool to the course. This reuses the same signed launch flow; it is not a new XBlock that stores DRM-X credentials in Studio.
Map resources and set policies#
Create a resources entry with title, Content ID, content type, policy, provider=lti and enabled=true. In the registered platform entry, map the LMS resource-link ID to that resource. An unmapped launch is denied and shows the resource ID to the signed-in launcher for administrator setup.
The bridge verifies the signature, issuer, audience, deployment, nonce, expiry, message type, target URL and course role. Launch state is consumed once. The player receives a short-lived session handle; DRM-X credentials remain on the server.
Qualification and access changes#
Local tests validate real RSA-signed launch tokens and reject mismatched claims. Canvas, Blackboard, Brightspace and Open edX tenant acceptance is still required. Do not describe this preview as certified LTI Advantage support.
The bridge session handle expires after 15 minutes. It does not call the LMS to recheck enrollment during that interval. Removing a learner may therefore leave an already issued handle usable until it expires; an issued DRM license follows its own policy lifetime. Reopen the lesson for a fresh launch.