Issues: w3c/webauthn
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
supplementalPubKeys attestation incompatible with most verification procedures
subtype:extensions
type:technical
#2075
opened May 20, 2024 by
emlun
Support for WebDriver BiDi
stat:Discuss
subtype:FeatureProposal
#2072
opened May 16, 2024 by
jimevans
Remove the UVM extension from WebAuthn L3 (potentially)
type:technical
#2069
opened May 9, 2024 by
timcappalli
Empty strings are not valid RFC 8266 Nicknames
type:technical
#2068
opened May 4, 2024 by
zacknewman
Authenticator data flags reserved bits must be 0 or the figures would ideally be changed
type:editorial
#2063
opened Apr 29, 2024 by
zacknewman
Additional guidance/clarification on RP ID and origin validation
type:technical
#2059
opened Apr 21, 2024 by
zacknewman
excludeCredentials on Get
@Risk
Items that are at risk for L3
stat:Discuss
subtype:FeatureProposal
type:technical
#2057
opened Apr 19, 2024 by
christiaanbrand
Deprecate AuthenticatorAttachment in favor of PublicKeyCredentialHints.
type:technical
#2053
opened Mar 27, 2024 by
akshayku
Editorial convention: Semantic line breaks
type:editorial
type:process
#2045
opened Mar 18, 2024 by
emlun
New Authenticator Extension: Time Since UV
stat:Blocked
Prerequisites are not yet satisfied
type:technical
#2034
opened Feb 28, 2024 by
timcappalli
Defining new OIDs to facilitate WebAuthn interoperability with CMS
@Risk
Items that are at risk for L3
type:editorial
#2026
opened Feb 16, 2024 by
corrideat
Reflect caching of user gestures in WebAuthn assertion
stat:Blocked
Prerequisites are not yet satisfied
type:technical
#2023
opened Feb 14, 2024 by
rlin1
Revised txAuthSimple extension
stat:Blocked
Prerequisites are not yet satisfied
type:technical
#2022
opened Feb 14, 2024 by
rlin1
rp.name, user.name and user.displayName length limit does not state binary encoding
i18n-needs-resolution
Issue the Internationalization Group has raised and looks for a response on.
stat:pr-open
type:technical
Ambiguous instructions in the Android Key Attestation Statement Format verification procedure
@Risk
Items that are at risk for L3
type:technical
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.