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





On Fri, Aug 26, 2022 at 12:27 PM Steven Valdez <[email protected]> wrote:

> 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
> <https://urldefense.com/v3/__https://chromestatus.com/feature/5078049450098688__;!!Op6eflyXZCqGR5I!EpQtGt18KpZ6Fw7kFH7gN63MbhpP9Mvf6h6nOX703NaoatMpb9lx6HtZ8itngItoD63x5mstF30VWd0$>
>
> 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/
> <https://urldefense.com/v3/__https://www.chromium.org/updates/trust-token/__;!!Op6eflyXZCqGR5I!EpQtGt18KpZ6Fw7kFH7gN63MbhpP9Mvf6h6nOX703NaoatMpb9lx6HtZ8itngItoD63x5mst59NpqFg$>
> .
>
>
> On Fri, Aug 26, 2022 at 1:23 PM 'Yan Han' via blink-dev <
> [email protected]> wrote:
>
>> 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:
>> [image: Screen Shot 2022-08-22 at 3.56.25 PM.png]
>>
>> Can we get more information about this error msg and how to fix this
>> issue?
>>
>> Thanks,
>> Yan
>>
>> --
>> 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 [email protected].
>> 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
>> <https://urldefense.com/v3/__https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACvv7Wd7vEX*3Dhkz524tT47VYABEwjrrkrvG-QM2LfK7iUXfGtw*40mail.gmail.com?utm_medium=email&utm_source=footer__;JSU!!Op6eflyXZCqGR5I!EpQtGt18KpZ6Fw7kFH7gN63MbhpP9Mvf6h6nOX703NaoatMpb9lx6HtZ8itngItoD63x5mstr7P5l0c$>
>> .
>>
>
>
> --
>
>  Steven Valdez |  Chrome Privacy Sandbox |  [email protected] |  Cambridge,
> MA
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACvv7WcC66pbk-HgnRKWyuK9hXPD%2Ba7dse7-Vodr6gjWRHbHjg%40mail.gmail.com.

Reply via email to