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.

Sign up for GitHub

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

Jump to bottom

For +jwt iat MUST be an integer #22

Open
OR13 opened this issue Feb 22, 2025 · 3 comments
Open

For +jwt iat MUST be an integer #22

OR13 opened this issue Feb 22, 2025 · 3 comments

Comments

@OR13
Copy link
Collaborator

OR13 commented Feb 22, 2025 •
edited
Loading

A media type of +jwt implies conformance to JWT, however the test suite currently contains examples with iat being a string.

This causes off the shelf jwt libraries to fail.

Fix the test suite so that setting an invalid iat causes a failure.
@OR13
Copy link
Collaborator Author

OR13 commented Feb 22, 2025

Also, the JSON-LD context for v2 clearly states that iat is a non negative integer:

https://github.com/w3c/vc-data-model/blob/main/contexts/credentials/v2#L313

@selfissued
Copy link

Can you file an issue on this in https://github.com/w3c/vc-jose-cose-test-suite ? Thanks.

@brentzundel
Copy link
Member

This seems to be an issue with the test suite rather than with the specification.
I am moving this issue there.

@brentzundel brentzundel transferred this issue from w3c/vc-jose-cose Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@selfissued @OR13 @brentzundel