We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
FIDO has changed the MDS3 blob schema without updating the spec:
MetadataStatement.friendlyNames (affects every entry)
MetadataStatement.friendlyNames
Appears to be a Map<String, String> of language code to name.
Map<String, String>
"friendlyNames": { "en-US": "ID-One Card" }
BiometricAccuracyDescriptor.iAPARThreshold (eg: "YubiKey Bio Series - Multi-protocol Edition")
BiometricAccuracyDescriptor.iAPARThreshold
{ "userVerificationMethod": "fingerprint_internal", "baDesc": { "selfAttestedFRR": 0.0, "selfAttestedFAR": 0.0, "iAPARThreshold": 0.0, "maxTemplates": 12, "maxRetries": 8, "blockSlowdown": 0 } },
Unclear what we do with this.
StatusReport.certificationProfiles (eg: "Ensurity AUTH BioPro")
StatusReport.certificationProfiles
"certificationProfiles": ["consumer"],
fido-mds treats all unknown fields as errors (because it could be security sensitive).
fido-mds
I've emailed FIDO asking for this to be documented properly – so fixing this properly may be blocked on them.
The text was updated successfully, but these errors were encountered:
micolous
Successfully merging a pull request may close this issue.
FIDO has changed the MDS3 blob schema without updating the spec:
MetadataStatement.friendlyNames
(affects every entry)Appears to be a
Map<String, String>
of language code to name.BiometricAccuracyDescriptor.iAPARThreshold
(eg: "YubiKey Bio Series - Multi-protocol Edition")Unclear what we do with this.
StatusReport.certificationProfiles
(eg: "Ensurity AUTH BioPro")fido-mds
treats all unknown fields as errors (because it could be security sensitive).I've emailed FIDO asking for this to be documented properly – so fixing this properly may be blocked on them.
The text was updated successfully, but these errors were encountered: