fix: handle the zero cases for oidc.Time #339
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Time fields was not set in JSON, the zero value
0
, resulted in a non-zerotime.Time
in conversion. This made verifier checks against a zero (unset) time always pass:oidc/pkg/oidc/verifier.go
Line 179 in 5a14f8d
This bug was most likely introduced in #283 refactorings.
Likewise, passing an empty time to
oidc.FromTime
now results in a0
value for the JSON.