Add support for credProtect extension

[emlun]

See: https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html#sctn-credProtect-extension

[github-actions]

Test Results

2 251 tests   2 243 ✅  58s ⏱️
   46 suites      8 💤
   46 files        0 ❌

Results for commit 613d34f.

♻️ This comment has been updated with latest results.

[ethantmcgee]

We did not expect this go from us asking about it on a random Thursday to seeing a PR merged in such a short time. Thank you so much!

[emlun]

@ethantmcgee Sorry for the delay, but this is now available on Maven Central in pre-release 2.7.0-RC1. Please try it out and let us know if it works! This pre-release will be promoted to an official 2.7.0 release on 2025-05-15 if no issues come in before then.

[ethantmcgee]

@emlun thanks so much for adding this, we were able to put this into the project today and test. It doesn't appear the generated json is correct. When I setup the options that we want via demo.yubico.com it shows that the extensions setup is

"extensions": {
    "credProps": true,
    "credentialProtectionPolicy": "userVerificationRequired",
    "enforceCredentialProtectionPolicy": true
},

which seems to line up with the mozilla documentation.

The webauthn library is instead generating

"extensions": {
    "credProps": true,
    "credProtect": {
        "credentialProtectionPolicy": "userVerificationRequired",
        "enforceCredentialProtectionPolicy": true
    }
}

We are configuring the extensions as follows:

var extensions = RegistrationExtensionInputs.builder()
      .credProps()
      .credProtect(Extensions.CredentialProtection.CredentialProtectionInput.require(UV_REQUIRED));

Please let me know if I've done something incorrectly and thanks again!

[emlun]

Well that's embarrassing 😆 good catch, thanks!

[emlun]

This should be fixed in 2.7.0-RC2, available now on Maven Central. Care to test that too?

[ethantmcgee]

2.7.0-RC2 passes all of our tests. Thanks!

We look forward to the release.