You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: explainer.md
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,14 @@ Here is an example of how the the API might be used in practice:
56
56
```
57
57
You can read a more detailed and technical description of the API in the [specification draft](https://wicg.github.io/digital-identities/).
58
58
59
+
### Using the API from another origin
60
+
61
+
The specification allows usage of the API from a remote/third-party origin via the "digital-credentials-get" Permissions Policy. This is useful for scenarios where a website wants to request digital credentials from a wallet provider that is hosted on a different origin. The Permissions Policy can be set on an iframe that embeds the website that wants to use the API. Here is an example of how the Permissions Policy can be set on an iframe:
62
+
63
+
```HTML
64
+
<iframeallow="digital-credentials-get"></iframe>
65
+
```
66
+
59
67
## Horizontal reviews
60
68
61
69
*[Security and privacy TAG Questionnaire](horizontal-reviews/security-privacy.md)
0 commit comments