Closed
Description
At TPAC, we heard that WebAuthn extensions must be filed in an IANA registry to be official: https://www.iana.org/assignments/webauthn/webauthn.xhtml#webauthn-extension-ids
There are two extensions related to SPC:
payment
, which is set by the calling website at creation time, and is set internally by the browser at authentication time.thirdPartyPayment
, which is spec'd in CTAP 2.1 (yet to be released).
However currently the payment
extension does too much, as per SPC: From browser cache to FIDO/WebAuthn integration. Long term, thirdPartyPayment
will be the creation-time way to indicate that a credential can be used for third-party payment flows, and payment
becomes an authentication-time only extension.
I am not currently sure if we should register these extensions in IANA soon, or wait until we reach some future stable state before doing so, but filing this to track doing the registration.
Metadata
Metadata
Assignees
Labels
No labels