commit 954305955194f3cbd4c4ab8b2dd908ac3e9618c9
author Liam Brady <lbrady@google.com> Wed May 03 18:28:34 2023
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Wed May 03 18:28:34 2023
tree d0c7cebc0aa2e4eaa76124a7e4a78aac583f05d4
parent 47593abc37d6ab0e34ea7d07eb6ba71581687eb2

Add "Required Permissions To Load" to Fenced Frame Config.

Update FencedFrameConfig to include a new field:
required_permissions_to_load_. Previously, opaque-ads fenced frames
were always loaded with a static list of permissions which were always
enabled regardless of whether or not they were necessary. This was done
so that fenced frames loaded with an API can have access to the
necessary reporting tools (such as private aggregation).

However, not all config-generating APIs require all features to be
enabled in order to function properly. For instance, shared storage is
one of the enabled features, but FLEDGE does not need it.

With this change, config-generating APIs can now set the specific
permissions they require for a fenced frame to be enabled, and include
them directly in the configuration. This ensures that only the
necessary permissions are enabled, which enhances security for pages
loaded into fenced frames.

Fenced frames created without an API will now not allow any features in
their permissions policies.

This CL updates various tests to respond to this change.

Change-Id: Ifb3cadc561d1de178ebbc540073f27b9b026ccac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4334571
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Liam Brady <lbrady@google.com>
Cr-Commit-Position: refs/heads/main@{#1139026}