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

Not able to work using DRM as well as AES (with Token) #31

Open
prabhanshu opened this issue Jul 27, 2017 · 2 comments
Open

Not able to work using DRM as well as AES (with Token) #31

prabhanshu opened this issue Jul 27, 2017 · 2 comments

Comments

@prabhanshu
Copy link
Contributor

Problem is related to Authentication between Xblock and Azure Media Services.

We are using "Widevine" as PlayReady is not supported by Chrome. Adding Screenshot which may help you to debug the issue

screen shot 2017-07-12 at 10 10 01 pm

screen shot 2017-07-12 at 10 09 17 pm

screen shot 2017-07-12 at 10 06 38 pm

@prabhanshu
Copy link
Contributor Author

Any update on this, I am facing similar issue for AES (with token) also

screen shot 2017-08-07 at 11 05 38 pm

screen shot 2017-08-07 at 11 04 59 pm

screen shot 2017-08-07 at 11 04 40 pm

screen shot 2017-08-07 at 11 04 16 pm

@prabhanshu prabhanshu changed the title Not abe to work using DRM Not able to work using DRM as well as AES (with Token) Aug 7, 2017
@prabhanshu
Copy link
Contributor Author

Do we need "Azure Media Service Explorer" application for this (tried using through Web but it was not working)?.

After a long research figured that out that Bearer token used in Xblock is different then what it is mentioned in Azure portal. From web I dont know from where the bearer token value is generated, but when I used "Azure Media Service Explorer" I got the proper bearer token.

Verification Key used in Xblock:
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cm46bWljcm9zb2Z0OmF6dXJlOm1lZGlhc2VydmljZXM6Y29udGVudGtleWlkZW50aWZpZXIiOiJhMzY5MGY3ZC05ZWRjLTRmMTUtYWVhYi1hZmY1ODcyZDdlYzMiLCJpc3MiOiJodHRwOi8vb3Blbi5lZHgub3JnLyIsImF1ZCI6InVybjp4YmxvY2stYXp1cmUtbWVkaWEtc2VydmljZXMiLCJleHAiOjE1MDIxMzQ0MjEsIm5iZiI6MTUwMjEzMDUyMX0.nANjC-tks2NxLhn2n9ywQCevhnyYLltCYGGvsa5LM-s

which I didn't find anywhere in azure portal.

Just wanted to know is it necessary to use "Azure Media Service Explorer" to get the proper bearer token value for our content protected assets

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

1 participant