Question about running Trust Token in Chrome

[Yan Han]

Hello,

Our organization is trying to use Trust Tokens and we were able to test it locally up to 8 months ago with V2 PMB. But after that, it was not working anymore. We thought it was due to V3 update, but even after updating the configs to V3 PMB, it is still broken. 

The only error msg that we're seeing is shown below:

Can we get more information about this error msg and how to fix this issue?

Thanks,

Yan

[Steven Valdez]

I'm not sure about 8 months ago, but as of May (M101), the origin trial for Trust Token concluded: https://chromestatus.com/feature/5078049450098688

We are still in the process of updating the API and figuring out next steps, but in the meantime you can still enable the feature for local experimentation via command-line flags as described in https://www.chromium.org/updates/trust-token/.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACvv7Wd7vEX%3Dhkz524tT47VYABEwjrrkrvG-QM2LfK7iUXfGtw%40mail.gmail.com.

--

Steven Valdez |

Chrome Privacy Sandbox |

sva...@google.com |

Cambridge, MA

[Clayton j Salter Fear]

yees im wanting to know all about it too please

[Yan Han]

Hi Steven, 

Thank you so much for the info.

We did enable the TT feature by launching Chrome (98.0.4758.80) via command line by passing --enable-blink-features=TrustTokens,TrustTokensAlwaysAllowIssuance  --additional-trust-token-key-commitments='{...}' but still had the above error. 

From https://github.com/JackJey/trust-token-issuer-demo/issues/5#issuecomment-1223375871, the author mentioned TrustToken API is sensitive about the domain it's running. 

Do we need to register our domain for allowlist in order to test it manually?

Thanks,

Yan

[Steven Valdez]

You'll need "--enable-features=TrustTokens --enable-blink-features=TrustTokens,TrustTokensAlwaysAllowIssuance --additional-trust-token-key-commitments={...}"

The "enable-features" flag enables the feature in Chrome, while the "enable-blink-features" flag enables the feature regardless of a domain/site having the origin trial token.

[Steven Valdez]

Can you hit "Check for Updates" under "Trust Token Key Commitments" in "chrome://components", and then see whether hitting "Issue" on https://trusttoken.dev/ works (to see if its a problem with that issuer/custom key commitments or more generally).

On Tue, Aug 30, 2022 at 10:33 AM Yan Han <yan...@yahooinc.com> wrote:

Hi Steven,

Previously I enabled TrustTokens feature from the browser after starting Chrome. Now I tried to pass `--enable-features=TrustTokens` too, but still had the same issue. Also I noticed that the browse's complaining about `--enable-blink-features=TrustTokens,TrustTokensAlwaysAllowIssuance` saying they are not supported. My Chrome Version is: 98.0.4758.80 (Official Build) (x86_64)

  Any suggestions?

Thanks,

Yan

[Yan Han]

Hi Steven,

Previously I enabled TrustTokens feature from the browser after starting Chrome. Now I tried to pass `--enable-features=TrustTokens` too, but still had the same issue. Also I noticed that the browse's complaining about `--enable-blink-features=TrustTokens,TrustTokensAlwaysAllowIssuance` saying they are not supported. My Chrome Version is: 98.0.4758.80 (Official Build) (x86_64)

  Any suggestions?

Thanks,

Yan

On Tue, Aug 30, 2022 at 9:10 AM Steven Valdez <sva...@google.com> wrote:

[Yan Han]

 https://trusttoken.dev/ works. Got 200 OK and "Response: Issuing 1 tokens."

Thanks,

Yan

[Steven Valdez]

In that case, it sounds like the custom key commitments you're passing in through the command-line aren't correctly formatted or something. It's hard to debug without more specifics on the endpoint you're hitting/configured keys. If you're okay sharing details in private, perhaps open up a restricted Chromium bug (crbug.com) or we can discuss off-list.