[Openid-specs-ab] [openid/connect] iat/exp and IntDate/UTC is awkward (issue #823)
issues-reply at bitbucket.org
Thu Mar 28 12:23:03 UTC 2013
New issue 823: iat/exp and IntDate/UTC is awkward
for both JWT client auth types, it seems strange to define the time format for iat but not exp which comes first. Can we just defer to JWT's definition of IntDate and iat and exp?
This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.
More information about the Openid-specs-ab