-
Notifications
You must be signed in to change notification settings - Fork 3
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
Verification of expiry and issuance date #3
Comments
The "W3C Verifier" can decide to accept expired credentials that have verified successfully, afaik. The layering between W3C and OAuth is blurred in the current implementation, but should be addressed in our W3C CR1 rewrite. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do iat and exp get checked in the verify process? Afaik. they don't. The proposed verifier uses
jose.compactVerify(jws, publicKey);
which does not check on the dates. Neither this is done forvalidFrom
andvalidUntil
.Is the user supposed to do these checks? because i tested expired credentials and they verified.
The text was updated successfully, but these errors were encountered: