- From: Simone Onofri <simone@w3.org>
- Date: Wed, 8 Jul 2026 19:44:05 +0200
- To: Web Authentication Working Group <public-webauthn@w3.org>
- Cc: ANTHONY NADALIN <nadalin@prodigy.net>, Michael Jones <michael_b_jones@hotmail.com>
Hi all, I opened a few pull requests against the charter to address the security and privacy comments: https://github.com/w3c/charter-drafts/pulls?q=is%3Apr+is%3Aopen+%5Bwg%2Fwebauthn%5D Could you please take a look when you have a chance to see whether the proposed changes align with the group’s expectations? Thanks, Simone > On 8 Jul 2026, at 02:46, ANTHONY NADALIN <nadalin@prodigy.net> wrote: > > Here is the agenda for the 07/08/2026 W3C Web Authentication. WG Meeting, that will take place as a 30-minute teleconference. Remember, call is 12:00 PM Pacific Time. Reminder that we will be using ZOOM from now on, please make sure you go to Web Authentication bi-weekly (w3.org) > > Select scribe please someone be willing to scribe so we can get down to the issues > > • Here is the link to the Level 2 Webauthn Recommendation https://www.w3.org/TR/2021/REC-webaut > • L3 CR Web Authentication: An API for accessing Public Key Credentials - Level 3 > • Consensus to make L3 CR the L4 First Public Working Draft (Done) > • Consensus to request submitting for Recommendation (Done) > • TPAC 2026 - October 26-30th Dublin, Ireland - TPAC 2026 | 2026 | TPAC | Events | W3C > • Calendar | TPAC 2026 | W3C > • WebAuthn Recharter Discussion - Web Authentication Working Group Charter > • Rechartering WebAuthn · Issue #2388 · w3c/webauthn > • CANCELLED Meetings > • Meeting 07/22/2026 CANCELLED (IETF) > • Meeting 08/19/2026 CANCELLED > • Meeting 09/02/2026 CANCELLED (GDC) > • Meeting 10/28/2026 CANCELLED (TPAC) > • These were the topics discussed at 2025 TPAC: > • Discovery of migrated credentials · Issue #2340 · w3c/webauthn > • Add Credential Manager Trust Group Key (CMTG) extension · Issue #2338 · w3c/webauthn > • WebAuthn requestUserInfo -- easier account creation · Issue #2336 · w3c/webauthn > • Explainer for Level 4 · Issue #2297 · w3c/webauthn > • Update Credential Record to suggest storing RP ID as well for better Related Origins support · Issue #2257 · w3c/webauthn > • Should an RP be able to provide finer grained authenticator filtering in attestation options? · Issue #1688 · w/223c/webauthn > > • L3 Recommendation · Issues and open pull requests and open issues, these must be resolved before we go to Recomendation > • Editors, Contributors and Acknowledgements Review · Issue #2385 · w3c/webauthn > > • Pull requests · w3c/webauthn > • Support Algorithm Migration by akshayku · Pull Request #2437 · w3c/webauthn > • Adds additional hints for form factors by timcappalli · Pull Request #2387 · w3c/webauthn > • Deprecate Authenticator Attachment in favor of Hints by akshayku · Pull Request #2383 · w3c/webauthn > • Add new credential signature count parameter to Set Credential Properties virtual authenticator endpoint by MasterKale · Pull Request #2382 · w3c/webauthn > • Add fallbackUrl client extension for hybrid transport authentication by harshlal028 · Pull Request #2380 · w3c/webauthn > • Add "Credential Manager Trust Group (CMTG) Key" extension by timcappalli · Pull Request #2377 · w3c/webauthn > • [Do not merge yet] Add `requestUserInfo` by nsatragno · Pull Request #2358 · w3c/webauthn > > • L4 Issues · w3c/webauthn > • Post Quantum Crypto and WebAuthn Transition for RP · Issue #2417 · w3c/webauthn > • Call for editors for WebAuthn L4 · Issue #2406 · w3c/webauthn > • Virtual authenticator should allow `counter` to always be `0` · Issue #2363 · w3c/webauthn > • Client terminology hints for external authenticator form factors · Issue #2360 · w3c/webauthn > • Feature: Allow RP to opt out of certain transports · Issue #2349 · w3c/webauthn > • Add hybrid fallback URL extension · Issue #2341 · w3c/webauthn > • Discovery of migrated credentials · Issue #2340 · w3c/webauthn > • Add Credential Manager Trust Group Key (CMTG) extension · Issue #2338 · w3c/webauthn > • Same PRF regardless of UV? · Issue #2337 · w3c/webauthn > • WebAuthn requestUserInfo -- easier account creation · Issue #2336 · w3c/webauthn > • document and mitigate fingerprinting and disclosure risk of capabilities and extensions · Issue #2320 · w3c/webauthn > • Add a note about `appid` extension not compatible with related origin requests · Issue #2312 · w3c/webauthn > • Explainer for Level 4 · Issue #2297 · w3c/webauthn > • client extension results field name is unclear · Issue #2275 · w3c/webauthn > • Provide a way for an RP to indicate backup preference during credential registration for providers who support both backed-up and non-backed up credential · Issue #2252 · w3c/webauthn > • Missing tasks in parallel steps in Web Authentication: An API for accessing Public Key Credentials - Level 3 · Issue #2250 · w3c/webauthn > • Allow immediate mediation · Issue #2228 · w3c/webauthn > • `credProps` output directions contradict notes · Issue #2213 · w3c/webauthn > • "Verify" is undefined · Issue #2208 · w3c/webauthn > • JSON parsing should be on top of Infra primitives · Issue #2207 · w3c/webauthn > • Use of "valid domain" seems wrong · Issue #2206 · w3c/webauthn > • Usage of "effective domain" seems wrong · Issue #2205 · w3c/webauthn > • Handling of non-fully active documents for PublicKeyCredential methods · Issue #2184 · w3c/webauthn > • [Editorial] platform authenticator relationship to WebAuthn Client and Client Device · Issue #2164 · w3c/webauthn > • Add AAGUID to credProps · Issue #2157 · w3c/webauthn > • Add `challengeUrl` · Issue #2152 · w3c/webauthn > • Allow Conditional Mediation without autofill · Issue #2144 · w3c/webauthn > • UTF-8 decode should not be required for response.clientDataJSON and cData · Issue #2100 · w3c/webauthn > • Return more nuanced errors · Issue #2096 · w3c/webauthn > • [[Create]] should not access the global object directly · Issue #2092 · w3c/webauthn > • Add support for hinting at verbiage other than "sign in" during authentication · Issue #2086 · w3c/webauthn > • Additional guidance/clarification on RP ID and origin validation · Issue #2059 · w3c/webauthn > • excludeCredentials on Get · Issue #2057 · w3c/webauthn > • CollectedClientData serialization is confusing WebIDL and/or Infra values for ECMAScript values · Issue #2056 · w3c/webauthn > • Deprecate AuthenticatorAttachment in favor of PublicKeyCredentialHints. · Issue #2053 · w3c/webauthn > • Adding some sentences to describe credential sharing between multiple users · Issue #1921 · w3c/webauthn > • Update Authenticator Taxonomy examples section · Issue #1912 · w3c/webauthn > • Clarify the need for truly randomly generated challenges (aka challenge callback issue) · Issue #1856 · w3c/webauthn > • Prescriptive behaviours for Autofill UI · Issue #1800 · w3c/webauthn > • Provide passwordless example, or update 1.3.2. to be a passwordless example · Issue #1735 · w3c/webauthn > • Public Key Credential Source and Extensions · Issue #1719 · w3c/webauthn > • Split RP ops "Registering a new credential" into one with and one without attestation · Issue #1710 · w3c/webauthn > • Switch to permissive copyright license? · Issue #1705 · w3c/webauthn > • Platform Errors for attestations. · Issue #1697 · w3c/webauthn > • Should an RP be able to provide finer grained authenticator filtering in attestation options? · Issue #1688 · w3c/webauthn > • Lookup Credential Source by Credential ID Algorithm returns sensitive data such as the credential private key · Issue #1678 · w3c/webauthn > • Trailing position of metadata · Issue #1646 · w3c/webauthn > • [Editorial] Truncation description inaccurate · Issue #1645 · w3c/webauthn > • Mechanism for encoding *direction* metadata may need more work · Issue #1644 · w3c/webauthnRegarding the issue of Credential ID exposure(13.5.6), from what perspective should RP compare RK and NRK > • Unicode "tag" characters are deprecated for language tagging · Issue #1642 · w3c/webauthnSupport for remote desktops · Issue #1577 · w3c/webauthn > • CollectedClientData.crossOrigin default value and whether it is required · Issue #1631 · w3c/webauthn > • double check whether the Secure Payment Confirmation effort has implications on the WebAuthn spec · Issue #1492 · w3c/webauthn > • Regarding the issue of Credential ID exposure(13.5.6), from what perspective should RP compare RK and NRK and which should be adopted? · Issue #1484 · w3c/webauthn > • Clearly define the way how RP handles the extensions · Issue #1258 · w3c/webauthn > • export definitions? · Issue #1049 · w3c/webauthn > > • L4 No Assigned Milestone · w3c/webauthn > • Re-Open "confirmation" discussion (see PR#2020) · Issue #2352 · w3c/webauthn > • Missing validation of rpId before Related Origins fetch · Issue #2422 · w3c/webauthn > > • Other open issues or discussions > • Adjourn
Received on Wednesday, 8 July 2026 17:44:38 UTC