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

Private State Token API Development - Registration Required? #286

Closed
thegreatfatzby opened this issue Jan 16, 2024 · 1 comment
Closed

Comments

@thegreatfatzby
Copy link
Contributor

Coming to PST way after some of the other PS APIs, have read a lot but am not fluent so to speak so sorry if I'm missing something.

I was trying to play around with PST, issuing tokens to a test site, testing the redemption path, query APIs, etc. When trying to issue tokens I got a few errors which make perfect sense, one in particular:

"...DOMException: No keys currently available for PST issuer. Issuer may need to register their key commitments."

Spent some more time digging around: I see that registration is still required for usage (maybe not for long?), and I don't see any chrome://flags to bypass that for a particular site (similar to what you can do with the PS RM API attestation), and I don't think I've seen any dev guides in either of the Github repos or articles I've found.

Is there a doc on this? Or do we need to register to test?

@dvorak42
Copy link
Collaborator

Registration will continue to be required for the foreseeable future. Part of this is because the issuer needs to provide key material to get distributed to Chrome (this is also why there isn't a flag to bypass the requirement as the client would still need to get the key material).

We'll try to surface it a bit more on the dev documentation, but you can use a command-line flag to develop a new issuer as described under Experimenting here: https://www.chromium.org/updates/trust-token/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants