[Openid-specs-fapi] Issue #195: Lifetime for JARM JWT (openid/fapi)

Torsten Lodderstedt issues-reply at bitbucket.org
Wed Dec 5 15:05:10 UTC 2018


New issue 195: Lifetime for JARM JWT
https://bitbucket.org/openid/fapi/issues/195/lifetime-for-jarm-jwt

Torsten Lodderstedt:

Hi,

Do you have any recommended value for lifetime of authorization response
JWT like the authorization code in RFC 6749?

>From RFC 6749, 4.1.2. Authorization Response

code

     REQUIRED.  The authorization code generated by the

     authorization server.  The authorization code MUST expire

     shortly after it is issued to mitigate the risk of leaks.  *A*

*     maximum authorization code lifetime of 10 minutes is*

*     RECOMMENDED.*  The client MUST NOT use the authorization code

     more than once.  If an authorization code is used more than

     once, the authorization server MUST deny the request and SHOULD

     revoke (when possible) all tokens previously issued based on

     that authorization code.  The authorization code is bound to

     the client identifier and redirection URI.


If you have, it would be great if it is mentioned in the specification.

Responsible: Nat


More information about the Openid-specs-fapi mailing list