GitLab

In order to support EME origin isolation requirements, the
fuchsia::media::drm protocols were updated to give the client control
of the storage used for CDM user data. In particular, the client can
"add" data stores to the KeySystem to use for writing persistent CDM
user data to. The API changes also inverted the provisioning flow and
puts the platform KeySystem service to control when a provisioning
request is initiated.

This CL adopts the use of the new APIs in the FuchsiaCdmManager. For
now, it adds a single shared drm::DataStore to each KeySystem. It also
provides a server implementation for the
fuchsia::media::drm::ProvisioningFetcher protocol, which is used by the
KeySystem for fetching provisioning certificates.

Bug: 991723
Change-Id: Ie799076be5be88abfda9519a0a9207a9667ad19d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318514
Commit-Queue: RJ Ascani <rjascani@google.com>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#803927}