Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is SPEKE mandatory for DRM integration between MediaPackage and DRM provider ? #42

Open
jorgebento opened this issue Dec 10, 2020 · 2 comments

Comments

@jorgebento
Copy link

jorgebento commented Dec 10, 2020

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 ?

image

Or at least may I connect media package to my drm server bypassing speke? just using api gateway ?

image

Regards

@andreasgangso
Copy link

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.

@jorgebento
Copy link
Author

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....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants