DRM-X 6.0Django protected video
Use Django authentication, admin-managed video mappings and time-limited access grants with the Universal Player.
How playback is authorized
Your backend decides who can watch. DRM-X provides playback authorization. The player uses that authorization to request a DRM license.
- Viewer
Signs in to your service and requests a video.
- Your backend
Checks the user's purchase, subscription, or other permission to watch.
- DRM-X
Applies the selected playback rules and returns the playback configuration and authorization.
- Player
Uses the returned authorization to request the DRM license needed for playback.
Install the Django app#
Install the django directory from the source bundle into your application environment. Add drmx to INSTALLED_APPS, include drmx.urls, enable Django session and authentication middleware, and run migrations. Keep CsrfViewMiddleware enabled.
pip install ./django
python manage.py migrate
# urls.py
path("protected/", include("drmx.urls"))Configure credentials and content#
Define settings.DRMX using SITE_ID, SITE_KEY, ACCESS_KEY, INSTANCE_ID and optional POLICY. Load secrets from your host environment. INSTANCE_ID is a stable site identifier used to separate playback subjects across applications.
In Django admin, open Protected videos and add a record. The DRM-X 6.0 Universal Player section groups Content ID, content type, protection policy and enabled state, with help for each field. Create an AccessGrant for the authenticated user, including start time and optional expiry. An enabled video alone does not grant access; revoking the grant or disabling the video prevents new playback requests.
Open /protected/VIDEO_ID/ after signing in. The page requests a session from /protected/VIDEO_ID/session/. For an existing course or subscription model, replace can_play with your server-side rule and retain the checks for active users, enabled videos and the exact requested video.
CSRF and deployment#
The released Web Component does not support custom session headers. This app places a masked Django CSRF token in the same-origin endpoint URL and explicitly validates it with Django’s normal cookie and origin checks. Do not remove that validation or enable shared caching for player pages.
Keep query strings out of access logs, use HTTPS and secure session cookies, and keep the supplied no-referrer behavior. Six tests cover access lifecycle, CSRF, origin, content binding and server-owned identity/policy on Django 6.0.8. Actual DRM playback still requires your published content.