JARM: expires_in should be a number

[Joseph Heenan]

https://openid.net/specs/openid-financial-api-jarm-ID1.html#response-type-token

has an example:

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

I believe expires_in should be a number, not a string, as per RFC6749.

[Joseph Heenan]

I think this mistake exists in all jws samples too.

[Brian Campbell]

This came up before with issue #176 and was "fixed" with 61e9fb3.

However, you are correct that some of the JWT/JWS samples were overlooked and still need to be fixed.

[Brian Campbell]

fixed with 8e1ef70