Okta, a very large WebAuthn Relying Party, is excited about this feature.
It addresses one of the top complaints we hear about passkeys which is
"orphaned passkeys" in authenticators when they are deleted from the user
account at the RP.
tim
On Wed, Sep 25, 2024 at 2:26 PM Alex Russell
wrote:
>
Hi Alex,
We have the following end-to-end example in the explainer that shows how
this would work for a more real example:
https://github.com/WICG/attribution-reporting-api/blob/main/attribution_scopes.md#attribution-scope-examples
Let me know if you have any questions on the example! We are al
Thanks, Ken. I suspected most of this, but thanks for filling in the
background and detail.
Again, I'm happy to let this go forward, just wanted to clarify how this
can go more smoothly in the future, particularly re: putting this kind of
thing in an Explainer and filing early w/ the TAG.
Best,
Hi Muyao,
The ChromeStatus entry says it's shipping in M131 but the implementation
status is still set to "In Development", which I think is preventing it
from appearing in the Roadmap page: https://chromestatus.com/roadmap
Because it didn't appear in the Roadmap, I thought it had been postpone
Hey Akash,
That example was the one I was referring to when asking for more. This
doesn't show a full in-situ example of how to use this or what code would
have been necessary before (or what the "before" code's deficiencies were).
Best,
Alex
On Thu, Sep 26, 2024 at 11:07 AM Akash Nadan wrote:
Amazing; thanks for letting us know!
On Thu, Sep 26, 2024 at 10:22 AM Tim Cappalli wrote:
> Okta, a very large WebAuthn Relying Party, is excited about this feature.
> It addresses one of the top complaints we hear about passkeys which is
> "orphaned passkeys" in authenticators when they are del
