mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2025-08-05 21:14:25 -04:00
add more token info
This commit is contained in:
parent
9dcbaad11e
commit
88b7facf8a
1 changed files with 6 additions and 0 deletions
|
@ -150,6 +150,12 @@ The client presents tokens to the Origin once they're provided by the issuer.
|
|||
|
||||
<small aria-hidden="true">Illustration: [Cloudflare](https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/)</small>
|
||||
|
||||
The tokens need to identify which issuers are trusted.
|
||||
|
||||
They can also be interactive or non-interactive. Interactive means that you need a fresh token based on the challenge, whereas a non-interactive token can be stored for later use.
|
||||
|
||||
Tokens can also be constrained to one specific Origin or they can be used across Origins.
|
||||
|
||||
### Private State Tokens
|
||||
|
||||
[Private State Tokens](https://developers.google.com/privacy-sandbox/protections/private-state-tokens) are a [proposed browser API](https://github.com/WICG/trust-token-api) by Google as part of their [Privacy Sandbox](https://developers.google.com/privacy-sandbox). They're based on the Privacy Pass protocol.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue