FIDO2 Server - MDS3 blobs invalid data

[josephp-is]

By submitting this issue you are acknowledging that any information regarding this issue will be publicly available.

If you have privacy concerns, please email conformance-tools@fidoalliance.org

FIRST PRE CHECK

• [x] I SOLEMNLY SWEAR THAT I HAVE SEARCHED DOCUMENTATION AND WAS NOT ABLE TO RESOLVE MY ISSUE

What protocol are you implementing?

• [x] FIDO2 Server
• [ ] CTAP2.0
• [ ] CTAP2.1
• [ ] UAF 1.1
• [ ] U2F 1.1
• [ ] U2F 1.2

NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.

What is your implementation class?

• [ ] Security Key / FIDO2 / U2F authenticators
• [x] Server
• [ ] UAF Client-ASM-Authenticator combo
• [ ] UAF Client
• [ ] UAF ASM-Authenticator

If you are platform authenticator vendor, please email conformance-tools@fidoalliance.org

What is the version of the tool are you using?

v1.7.18

What is the OS and the version are you running?

For desktop tools

• [ ] OSX
• [x] Windows
• [ ] Linux

For UAF mobile tools

• [ ] iOS
• [ ] Android

Issue description

Based on https://fidoalliance.org/specs/mds/fido-metadata-statement-v3.0-ps-20210518.html#dom-metadatastatement-userverificationdetails , the name of the field in the array should be "userVerificationMethod". However when I used https://jwt.io/ to decode the blobs which I downloaded from https://mds3.fido.tools/ , the name of the field is "userVerification" which is incorrect, as shown below.

    "userVerificationDetails": [
      [
        {
          "userVerification": "none"
        }
      ],
      [
        {
          "userVerification": "presence_internal"
        }
      ],
      [
        {
          "caDesc": {
            "base": 10,
            "minLength": 4
          },
          "userVerification": "passcode_external"
        }
      ],
      [
        {
          "caDesc": {
            "base": 10,
            "minLength": 4
          },
          "userVerification": "passcode_external"
        },
        {
          "userVerification": "presence_internal"
        }
      ]
    ]

Reference BLOBs

• https://mds3.fido.tools/execute/676db709ecc5d49535b1eaf7e6588a58c66ac5b3d59a03cbf698d34033d80f7f
• https://mds3.fido.tools/execute/b6c86e77771020cd84d7b124e70322a15697cb3d1f7e598933f46fa0a00024e9
• https://mds3.fido.tools/execute/edbd1d8477d07bc0f497016dce718a862d30c46af805279766eefa341925114a
• https://mds3.fido.tools/execute/e93ab2ae27c355e677bfcd2e250170079ff03b9da65bf37e82d15f0c7d69e689
• https://mds3.fido.tools/execute/d21939cedff83df7198ad92395c8d4328ec6357a60bcf206e16dfcaef2d49376

Thank you in advance and I truly appreciate the time and effort used to look into this issue.

[josephp-is]

Hi Illia Irachek,

Please take note that this issue is not related to #748.

[iirachek]

I understand. Accidentally closed the issue in the wrong tab. :sweat_smile: This one is being worked on and will be resolved soon.

[josephp-is]

Thank you so much for the prompt response. Cheers!

[iirachek]

Should be fixed. Please visit https://mds3.fido.tools/ to get new endpoints for your server.

[josephp-is]

Indeed, this issue has been fixed. Thank you once again.