W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

[Bug 17660] need token relative with user identity for a new generateKeyRequest parameter

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Jul 2012 19:38:25 +0000
Message-Id: <E1Sm8vZ-0004Az-Hh@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17660

--- Comment #1 from David Dorwin <ddorwin@google.com> 2012-07-03 19:38:25 UTC ---
(In reply to comment #0)
> key server should know the keymessage is from who.
> So I think app can generate a token based on account infor of user in web
> portal.

That is one possible scenario, but not all scenarios will involve such a token.

> Thus the generateKeyRequest may change to
> generateKeyRequest(KeySystem,initData, token),then the CDM can bind the token
> into keymessage before return the keymessage to app.

Such binding assumes that the key system / CDM can support it.

> 
> BTW: in 8.2 use section
> first question also mention about it.

The answer to the question says, "The application can add this to the license
request (sent via XMLHttpRequest in the examples) or send it to the CDM via
generateKeyRequest() to be included in the license request." The last part of
the sentence is referring to combining it into initData somehow (in a key
system-specific way). It is TBD how well such combination will work.


The intent was to not bake a specific scenario that not all key systems would
support into the API. Still, we could consider adding some additional parameter
if the combination doesn't work well or we want to ensure that the initData
returned by the needkey event is always the same as the value passed to
generateKeyRequest(). (It's not clear that the latter will always be the case
anyway, especially depending on the outcome of [1].)

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17673

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 3 July 2012 19:38:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2012 19:38:28 GMT