Hello,

i followed

https://www.wowza.com/forums/content...DRM-encryption
and

https://www.wowza.com/forums/content.php?59-How-to-use-the-internal-method-of-AES-128-encryption-to-secure-live-or-VOD-streams-sent-to-Apple-iOS-devices-%28ModuleEncryptionHandlerCupertinoStreaming%29


in order to set up AES encryption for HLS VOD streams. I use internal Wowza key creation and delivery.

I am using IMediaStreamNameAliasProvider2 to hide actual streams from customers. This allows only requests with a specific format in order to do DB lookup in the background and serve the actual requested file.

Within a chunkfile i have the following problem:

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:2
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-KEY:METHOD=AES-128,URI="<RESOLVED URL>"
#EXTINF:2.0, <UNRESOLVED URL>
...

As you can see, the URL for the encyption key is presented as the resolved URL which should not be visible to the user (if someone looks into the chunk file) and it is again passed to the resolve logic which then failes because it is in a wrong (already resolved) format.

Is this intentional? Is there a property which needs to be set in oder to have aliases for encyption key URLs as well?

I am using WMS 4.4! Please help!

Regards,
Thomas