Hi Yury,
Thank you so much for the swift reply.
Making sure I got the scenario right - Nimble native DRM support is on the roadmap and in addition, the following scenario is currently working:
1. Nimble is used as edge server, re-streaming HLS from Wowza or IIS.
2. Wowza/IIS integrates with PlayReady so all content is encrypted on the disk ("in situ") - at the origin site and at the edge site.
3. The media player gets the encrypted data via HLS.
If the above works, would it be correct to state that the end user's player is doing the decryption by using Nimble to connect to the back end DRM system (e.g. the player calls Nimble; Nimble redirects the call to Wowza/IIS, which in turn interact with PlayReady server)?
Best regards,
Ilan