[Openid-specs-fapi] JARM: The type of the value of the expires_in in 4.1.2. Response Type "token"

Takahiko Kawasaki taka at authlete.com
Fri Sep 21 19:37:04 UTC 2018


Hello,

# A trivial editorial issue

*4.1.2. Response Type "token"
<https://openid.net/specs/openid-financial-api-jarm.html#response-type-token>*
in JARM shows an example of authorization response as follows:

{
   "iss":"https://accounts.example.com",
   "aud":"s6BhdRkqt3",
   "exp":1311281970,
   "access_token":"2YotnFZFEjr1zCsicMWpAA",
   "state":"S8NJ7uqk5fY4EjNvP_G_FtyJu6pUsvH9jsYni9dMAJw",
   "token_type":"bearer",
   "expires_in":"3600",
   "scope":"example"
}


In the example, the type of the value of the expires_in is "string", but it
should be "number" if we strictly follow the definition of expires_in which
is found in *A.14. "expires_in" Syntax
<https://tools.ietf.org/html/rfc6749?#appendix-A.14>* in RFC 6749.

A.14.  "expires_in" Syntax

   The "expires_in" element is defined in Sections 4.2.2 and 5.1:

     expires-in = 1*DIGIT



Best Regards,
Takahiko Kawasaki
Authlete, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20180922/9c83d0c5/attachment.html>


More information about the Openid-specs-fapi mailing list