[Openid-specs-fapi] Issue #251: refresh token expiry time (openid/fapi)

josephheenan issues-reply at bitbucket.org
Thu Jul 18 13:05:25 UTC 2019


New issue 251: refresh token expiry time
https://bitbucket.org/openid/fapi/issues/251/refresh-token-expiry-time

Joseph Heenan:

Both the UK \( [https://github.com/OpenBankingUK/read-write-api-docs-pub/blob/v3.1.3-draft1/profiles/read-write-data-api-profile.md#token-expiry-time](https://github.com/OpenBankingUK/read-write-api-docs-pub/blob/v3.1.3-draft1/profiles/read-write-data-api-profile.md#token-expiry-time) \) and Australian \( [https://consumerdatastandardsaustralia.github.io/standards/#scopes-and-claims](https://consumerdatastandardsaustralia.github.io/standards/#scopes-and-claims)  \) standards define \(different :disappointed: \) ways to pass back the refresh token expiry time.

It may make sense for FAPI to define a standard mechanism?




More information about the Openid-specs-fapi mailing list