An important change in Google Chrome’s DRM behavior has been made that may affect customer integrations and may need action.
Starting with Chrome version 142 (and observed in some of the latest minor releases of version 141), Chrome now includes support for PlayReady DRM (com.microsoft.playready.recommendation).
This enhancement means Chrome can now support PlayReady SL3000, potentially impacting how DRM key systems are selected and managed within your service or playback workflows. Our product documentation and integration guides will be updated to reflect this expanded support.
Potential Impact
This notice applies if your account is encountering an increase in Error 7122 messages (ChallengeData is invalid) when Chrome attempts to issue a Widevine license using PlayReady challenge data.
The aforementioned error typically occurs when DRM keySystem selection and token-generation logic are not explicitly distinguished by browser type, under the assumption that Chrome only uses Widevine.
Recommended Action
To prevent Error 7122 and ensure proper license handling:
- Update your player configuration to explicitly declare the DRM keySystem (Widevine or PlayReady) per browser.
- Verify that your token-generation and license-issuance logic aligns with the detected keySystem.
- You can reference examples showing how to declare the appropriate DRM per player type here:
DoveRunner Multi-DRM Integration Samples for HTML5 Players
https://github.com/doverunner/html5-player-drm-samples
Our updated integration guides and scenario recommendations reflecting Chrome’s PlayReady support will be updated shortly.
If you have queIf you have questions or need assistance with your integration, please contact our Technical Support via the HelpCenter.
Thank you.
DoveRunner Team