Skip to content
New issue

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-mds-tool list-fido2 fails with InvalidJwt error #453

Closed
Be-ing opened this issue Nov 16, 2024 · 2 comments
Closed

fido-mds-tool list-fido2 fails with InvalidJwt error #453

Be-ing opened this issue Nov 16, 2024 · 2 comments

Comments

@Be-ing
Copy link

Be-ing commented Nov 16, 2024

I did this

$ cargo install fido-mds-tool
$ fido-mds-tool fetch
024-11-16T06:27:41.394418Z  INFO fido_mds_tool: Fetching from https://mds.fidoalliance.org/ to "/tmp/mds.blob.jwt"
2024-11-16T06:27:43.628861Z  INFO fido_mds_tool: Ok!
$ fido-mds-tool list-fido2 -p /tmp/mds.blob.jwt -d   
2024-11-16T06:27:50.919779Z DEBUG fido_mds::mds: X509VerifyResult { code: 0, error: "ok" }
2024-11-16T06:27:50.919850Z DEBUG fido_mds::mds: res=Ok(())
2024-11-16T06:27:50.944921Z ERROR fido_mds_tool: e=InvalidJwt

I also tried running fido-mds-tool from the kanidm/tools container: podman run -i -t docker.io/kanidm/tools:latest /bin/sh then repeat the above commands.

I expected the following

JSON output to pass to Kanidm client as described at https://kanidm.github.io/kanidm/stable/accounts/account_policy.html#setting-webauthn-attestation-ca-lists

What actually happened

fido-mds-tool always fails with an InvalidJwt error

Version (and git commit)

0.5.0

Operating System / Version

Fedora 41

@Be-ing Be-ing changed the title fido-mds-tool list-fido2 fails with InvalidJwt error fido-mds-tool list-fido2 fails with InvalidJwt error Nov 16, 2024
@Be-ing Be-ing changed the title fido-mds-tool list-fido2 fails with InvalidJwt error fido-mds-tool list-fido2 fails with InvalidJwt error Nov 16, 2024
@Firstyear
Copy link
Member

Duplicate of #450

This is because FIDO updated the MDS syntax without updating the specification and have ceased answering our emails.

@Be-ing
Copy link
Author

Be-ing commented Nov 19, 2024

Yikes. That's concerning and disappointing :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants