format of updated_time claim?

[Brian Campbell]

http://openid.net/specs/openid-connect-messages-1_0-16.html#StandardClaims

"updated_time string Time the End-User's information was last updated, represented as a RFC 3339 [RFC3339] datetime. For example, 2011-01-03T23:58:42+0000."

I've often wondered why updated_time uses a different format than other date claims. Is there a reason it can't be a JWT IntDate? If so, that be nice. If not, a brief explanation would be helpful. I can't be the only one that's had (or will have) this question.

[Brian Campbell]

It was said on the (Mar 28) call that this was used because it was what facebook's implementation was/is doing. Which might need to be a consideration.

[Michael Jones]

Facebook uses ISO 8601 update_time values. RFC 3339 is a profile of the ISO spec.

We will change this to "updated_at" and use the same time format as "exp", etc.

[Michael Jones]

Fixed #825 - Replaced "updated_time" with "updated_at".

→ <<cset 66e65b3096dd>>