You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You don't need to use this reference server.
But as far as I know, whatever URL you enter needs to be a server that implements SPEKE.
So you need to check with your DRM provider if they have a SPEKE url you can use.
Thank you, In the meantime I was able to deploy a mock drm server that basically always respond same speke xml file but with real keys retrieved from my drm provider. For dash+cenc you can use a cpix compliant xml but for hls+fairplay need to format xml file with speke tags otherwise does not work.
Media converter can talk directly to drm server, does not need aws api gateway
Media packager only works via api gateway, so you need to intermediate the communication using api gateway.
For vod content is straigh forward but for live channels did not worked already....
Hi All,
Do I need to use SPEKE in order to stablish a communication between media Package and DRM provider?
I mean may I fill the key proxy address with my server ? Is it possible to mediapackage retrieves keys directly on my server ?
Or at least may I connect media package to my drm server bypassing speke? just using api gateway ?
Regards
The text was updated successfully, but these errors were encountered: