Add FIDO2, WebAuthn and CTAP 2.3 support#619
Merged
Merged
Conversation
Test Results 1 files 1 suites 5m 17s ⏱️ Results for commit fcd4c30. ♻️ This comment has been updated with latest results. |
veikkoeeva
force-pushed
the
fido2
branch
6 times, most recently
from
July 15, 2026 21:39
45ea3b6 to
77d19a2
Compare
WebAuthn relying party - Add registration and assertion ceremony verification with clause-level W3C L3 checks. - Add packed, tpm, android-key, fido-u2f and none attestation verifiers with X.509 chain and profile checks on both crypto backends. - Add creation and request options builders, extension outputs, appid and related origins handling. - Add L3 JSON wire readers and envelope carriers. - Generalize COSE keys into Verifiable.JCose with RSA support. CTAP 2.3 - Add an authenticator simulator built as a pushdown automaton with injected crypto backends, plus the NFC/APDU transport profile. - Add makeCredential, getAssertion, getNextAssertion and getInfo with packed self and certified attestation. - Add clientPIN with PIN/UV auth protocols 1 and 2; HKDF-SHA-256 lands in the cryptography layer. - Add credentialManagement, authenticatorConfig, reset, bioEnrollment and largeBlobs. - Add enterprise attestation and the credProtect, minPinLength, largeBlobKey, hmac-secret and hmac-secret-mc extensions. - Advertise FIDO_2_3 honestly: the section 9 mandatory set is implemented, with every normative clause ledgered (155 implemented and tested, 70 profile conditional, 12 tracked missing of 237 assessed). - Prove the ceremonies over real wires: APDU transport and a Kestrel-hosted HTTP relying party. - Certify TPM-resident credential keys through TPM2_Certify against the in-house TPM simulator. Metadata service - Add metadata BLOB verification with entry well-formedness guards, serial-number monotonicity and revocation posture seams. - Add FIDO2 CLI verbs for inspection and metadata work. OAuth client - Add token-exchange and JWT-bearer request builders with client secret attach helpers; RFC 8693, RFC 7523 and RFC 6749 section 2.3.1 obligations verified end to end. Supporting - Zero secret copies at the provider boundaries and keep wire values in named pooled carriers. - Widen cryptographic event provenance to every signing surface. - Move the builder base to Verifiable.Foundation and update Lumoin.Base to 0.0.6.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WebAuthn relying party
CTAP 2.3
Metadata service
OAuth client
Supporting