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

Add Permission Policy #132

Merged
merged 8 commits into from
Jul 15, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -272,6 +272,16 @@ <h3>
The <dfn data-dfn-for="DigitalCredential">data</dfn> member is the
credential's response data.
</p>
<h3>
[[\DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors)
internal method
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WebAuthn seems to say we can't do this here due to lack of access to the settings object. I haven't looked into the details though, WDYT?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, right! I need to add it to the Cred Man itself! That's what they do for WebAuthn. I'll do that.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

</h3>
<ol>
<li>If |document| is not [=allowed to use=] the
<a>"digital-credentials-get"</a> permission, then [=exception/throw=] a
{{"NotAllowedError="}} {{DOMException}}.
</li>
</ol>
<h3>
[[\Store]](credential, sameOriginWithAncestors) internal method
</h3>
Expand Down Expand Up @@ -309,6 +319,29 @@ <h3>
<dfn class="export" data-dfn-for="DigitalCredential">[[\discovery]]</dfn>
whose value is "remote".
</p>
<section class="informative">
<h3>
User consent
</h3>
<p>
The <cite>Digital Credential API</cite> is a [=powerful feature=] that
requires [=express permission=] from an end-user. This requirement is
normatively enforced when calling `navigator.identity.get()` via the
{{DigitalCredential\[[DiscoverFromExternalSource]](origin, options,
sameOriginWithAncestors)}} internal method.
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
</p>
</section>
<section id="permissions-policy" data-cite="permissions-policy">
<h2>
Permissions Policy integration
</h2>
<p>
This specification defines a [=policy-controlled feature=] identified
by the string <dfn class="permission">"digital-credentials-get"</dfn>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI we also kicked off the registration in the permissions policy spec here:

https://github.com/w3c/webappsec-permissions-policy/pull/549/files

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. I'll add WebKit there too.

[[permissions-policy]]. Its [=policy-controlled feature/default
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
allowlist=] is [=allowlist/'self'=].
</p>
</section>
<h2 id="protocol-registry">
Registry of protocols for requesting digital credential
</h2>
Expand Down