DRM 5.3.1 Release Notes describe the new features and the known issues in DRM 5.3.1.
Secure Stop - You can specify whether playback stops or continues at the end of a playback window.
Resolution Based Output Protection (RBOP) - You can specify the output constraints based on pixel resolutions.
CDM Gating - In order to support HTML5, Adobe has updated the Reference Implementation license server included with the Adobe Primetime DRM (formerly Adobe Access DRM) Java SDK to be able to consume all DRM protocol messages at a single URL endpoint. This consolidation of HTTP URL methods is necessary in order to comply with the HTML5 EME (Encrypted Media Extension) specification that is in turn required to be implemented by CDM (Content Decryption Module) DRM vendors. Previously, these were the only URL endpoints exposed by the Reference Implementation license server:
Now, all requests (originating from an HTML5 CDM) can be directed to a single endpoint: /req
This change is backwards-compatible with non-CDM platforms, such as Flash Player, Android, iOS.
Hasher.bat (flashaccess-hasher.jar) outputs log messages to
flashaccess-global.log.You must ensure that the
flashaccess-global.log file is in the same directory with Hasher.bat.
The output of some of the
Strings that are not fully JSON compliant or fully compliant in a stand alone manner (i.e., without composition of JSON structures).
Xbox key server accepts key requests that have the version value not equal to 1.
The Xbox key server should only support key requests that have the version equal to 1, but currently, the server accepts key requests where the version is not 1.
The Xbox key server should not accept policies that are outside of the validity date, but currently, the server accepts them regardless.
Several classes implement a toJSON() method that should return a JSON compliant representation of that object as a String, but currently the returned value is not fully JSON compliant.