-
Notifications
You must be signed in to change notification settings - Fork 8
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
Do we want to mention the WICG browser api? #148
Comments
@danielfett can you add a bit more context on this API and why it should be included/referenced? |
I can't remember when Daniel's back from holiday but as he opened this issue after a conversation we had perhaps I can usefully answer. It's the API here: https://wicg.github.io/digital-credentials/ The reason to mention it would be that it solves the cross device security problem for OpenID for Verifiable Presentations, as it uses very similar mechanisms to the cross device passkey presentation by adding bluetooth proximity into the mix. Potentially it even means that if you're having trouble deciding between different possible ways of doing things the availability of the API might push you towards using OID4VP to get cross device security. The main downside is that it's still under development so isn't technically stable nor widely available yet, but Apple & Google have demoed it working cross device between different OSes. |
@jogu there is a section on protocol recommendations, as well as on proximity. What we might do is add a reference to this as an example of a protocol that establishes proximity via Bluetooth in one or more sections. Do you think that would be sufficient to address the issue? |
Yes, I think so. I had a read of the latest draft with this in mind, I think it might be worthy of mentions:
|
No description provided.
The text was updated successfully, but these errors were encountered: