Problem:
An expiration of 0 which is a valid epoch time, is treated the same as no expiration. In the case of a expiration = 0, a token is validated when in fact it should be rejected as expired
Solution:
Check for undefined instead of truthy
Validation:
Added a new test case
Type of change:
[ ] Feature work
[x] Bug fix
[ ] Documentation
[ ] Engineering change
[ ] Test
[ ] Logging/Telemetry
Risk:
[ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
[ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
[x ] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)
Problem: An expiration of 0 which is a valid epoch time, is treated the same as no expiration. In the case of a expiration = 0, a token is validated when in fact it should be rejected as expired
Solution: Check for undefined instead of truthy
Validation: Added a new test case
Type of change:
Risk: