Mosaic update 16 June
Axinom releases new features and updates for Mosaic and all included service on a regular base. Here is a summary over the last two weeks.
Latest releases:
- Video Service R125
- Hosting Service R125
- DRM Key Service 1.21.4
See full release notes for all Mosaic services.
Video Service
We're making some technical changes starting this release to make the
Mosaic Managed Services more independent in terms of the release cadences.
The Video Service is the first to receive this treatment, and as a result
we've introduced a new library @axinom/mosaic-video-messages
that contains all the Message Settings of this service.
Video Service documentation.
Hosting Service
We made some changes to the RMQ vhost creation logic.
Now, for new environments created via the API (createEnvironment
),
the RMQ vhost & shovels to shovel messages belonging to your environment to-and-from
the Managed Services will not be automatically created.
However, they will still be automatically provisioned when you create a new
environment via the Admin Portal or when you deploy and Custom Services
through the Hosting Service.
Hosting Service documentation.
DRM Widevine API 6.28.1
- Exposed
X-AxDrm-ErrorCode
HTTP Header for clients that use CORS. This is a fairly new custom header which represents Axinom error codes. Currently, this header is only used in Concurrent Stream Limiting. - Updated Widevine License Server SDK from 19.0.2 to 19.0.6 (latest). No behavioral changes expected.
- Fixed Widevine "Client Token" (the main "client ID" for Chrome CDM-like clients) handling. Previously, since the update to License Server SDK v19, such clients appeared to support Client Tokens, even if they in reality did not (e.g. Firefox; Chrome with "persistentState" not set to 'required'). This led to the
recommended_client_id
andclient_token
to be reported incorrectly for such clients. One of the effects of this is the Concurrent Stream Limiting feature not being able to reliably track those clients. - Fixed CSL bug where Widevine "renewal" requests were mistaken for "new" requests. This prevented the session-based blocking method from working correctly.
- Fixed Widevine license service incorrectly enforcing some native standard claims (such as 'exp'), which resulted in 500 Internal Server error responses. Now only the Axinom-specific claims documented in the "License Service Message" documentation are enforced, as expected.
Full DRM release notes.