-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Usage of requireExpiration(Date expiration) #213
Comments
I've already put it into practice:
|
This issue has been automatically marked as stale due to inactivity for 60 or more days. It will be closed in 7 days if no further activity occurs. |
I'm closing this in favor of #474 - that issue will allow all sorts of custom validation other than |
I want to validate a received token and make sure that it has a Expiration Time set. It looks like the only way to do such a thing is with the requireExpiration(Date expiration) method. However this requires the Expiration Time to equal the expiration passed as a parameter. On the receiving side I have no clue what the expiration time is going to be. I just want to make sure an expiration time is present in the token.
I have the following questions:
How can I require the presence of an exp claim?
What is the use case for the requireExpiration(Date expiration) since typically anyone who wants to validate the exp claim can not know the exact value of the expiration date.
The text was updated successfully, but these errors were encountered: