An online course platform already knows whether a student can access a lesson. Adding protected video should use that decision instead of creating a second enrollment or purchase database inside the DRM system.
The DRM-X 6.0 Cloud Multi-DRM integration projects illustrate this pattern for WordPress, Moodle and custom web applications. Haihaisoft has published 15 public integration repositories that include LMS plugins, backend examples, reusable SDK packages and web player components.
Keep authorization in your application
The standard playback flow uses a DRM-X Content ID:
- Publish a protected video and register its DASH or HLS media URLs. With configured 1aicloud or supported S3 publishing, DRM-X can record those URLs during publication. If you host protected files on your own server, register their URLs first.
- Map the video or lesson in your application to its DRM-X Content ID.
- When a viewer requests playback, check your existing login, purchase, subscription or course enrollment rules on the backend.
- If the viewer is authorized, request playback information. The player receives the registered media URL and a DRM License Token for the DRM-X playback workflow.
Once the media URLs are registered, the player page can resolve them from the Content ID. There is no need to hard-code a separate manifest URL into every lesson page. Keep the Site ID, Site Key and Access Key on the backend, following the relevant integration guide.
Choose a starting point that fits your stack
For WordPress education sites, separate repositories cover LearnPress, LearnDash, Tutor LMS, Sensei LMS and MasterStudy LMS. They use a shared DRM-X Universal Player plugin that is installed once per WordPress site. The Moodle repository includes activity and filter plugins, with instructions for installation, server configuration and adding protected content to a course.
For custom applications, the published examples cover PHP, Laravel, ASP.NET Core, ASP.NET Framework, Python/Django, Node.js/Express and Java/Spring Boot with Vue. Frontend teams can examine player components for React, Next.js and Vue. Reference bridges are also available for LTI, hosted LMS platforms and Shopify.
The backend projects include SDK packages where applicable, alongside source code and examples. Django and Laravel provide authorization extension points so that an existing business system can supply the access decision. Each repository includes README files in English, Simplified Chinese and Spanish.
What to check before deployment
Start with one course and one protected video. Verify that a subscribed user can play it, that an unauthorized user cannot, and that the mapping remains correct when an enrollment expires or changes. Then test the specific browser, device and DRM path your audience will use.
The integration download center offers a complete package and individual platform downloads. You can also inspect the public GitHub repositories before choosing a sample.
The published code is open source under each repository's included license. DRM-X 6.0 Cloud Multi-DRM is a separate hosted service, and downloading the code does not include a service subscription. These website and LMS integrations are public previews, with continuing testing and improvements; available playback features depend on the DRM technology, browser, device and platform.
Disclosure: This article discusses a Haihaisoft product and was drafted with AI assistance.
Top comments (0)