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

Remove note around Payment extension #255

Merged
merged 1 commit into from
Jul 31, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -1011,12 +1011,7 @@ directly; for authentication the extension can only be accessed via
</dl>

: <dfn export>Client extension processing ([=registration extension|registration=])</dfn>
:: Note: Reading [[webauthn-3]] literally, these steps don't work; extensions
are injected at step 12 of `[[Create]]` and cannot really modify anything.
However other extensions ignore that entirely and assume they can modify any
part of any WebAuthn algorithm!

When [[webauthn-3#sctn-createCredential|creating a new credential]]:
:: When [[webauthn-3#sctn-createCredential|creating a new credential]]:

1. Modify step 2 (the check for *sameOriginWithAncestors*) as follows:

Expand Down
Loading