[Openid-specs-ab] Refresh token lifetime?

[Mischa Salle]

Hi Stuart, Joseph,

thanks for the very useful pointers.
I certainly would be in favour of a clear standard beyond FAPI (there
obviously is demand for something). Does it make sense to open an issue
in Connect instead?

Searching for refresh_token_expires_in also gave me a few hits for OPs
returning (additionally) a refresh_token_expires_at parameter.
But in any case it seems the banking use ID token claims, while the
social providers use a response parameter and usually support (if
anything) refresh_token_expires_in.

    Mischa

On Tue, Aug 27, 2019 at 10:37:07PM +1000, Stuart Low wrote:
> I don’t believe it’s a formal standard but there is a fair bit of
> support from OP’s for refresh_token_expires_in so it has become the
> defacto standard for what you’re mentioning below.
> 
> From some Linkedin documentation (https://developer.linkedin.com/docs/Refresh-Tokens-with-OAuth-2# <https://developer.linkedin.com/docs/Refresh-Tokens-with-OAuth-2#>):
> 
> refresh_token_expires_in — The number of seconds remaining before the
> refresh token will expire. The lifespan of refresh tokens is usually
> larger than Access tokens. The exact duration depends on the type of
> Refresh Tokens issued. The different types explained below in the
> document.

On Tue, Aug 27, 2019 at 01:37:33PM +0100, Joseph Heenan wrote:
> Hi Mischa
> 
> There are [at least] 3 different solutions in the wild, all mentioned in https://bitbucket.org/openid/fapi/issues/251/refresh-token-expiry-time 
> 
> Joseph
> 

-- 
Nikhef                      Room  H155
Science Park 105            Tel.  +31-20-592 5102
1098 XG Amsterdam           Fax   +31-20-592 5155
The Netherlands             Email msalle at nikhef.nl
  __ .. ... _._. .... ._  ... ._ ._.. ._.. .._..
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20190827/66f8de7a/attachment.asc>