I have read the PODIO documentation. I have in particular contemplated the following statement concerning use of the refresh_token
:
This
The answer of your question:
Does this mean that the refresh_token will be indefinitely valid or does it expire?
...can be concluded from the section 1.5 and section 10.4 of the OAuth 2.0 specification.
Section 1.5 Introduction of refresh_token states:
Refresh tokens are issued to the client by the authorization server and are used to obtain a new access token when the current access token becomes invalid or expires, or to obtain additional access tokens with identical or narrower scope (access tokens may have a shorter lifetime and fewer permissions than authorized by the resource owner)
section 10.4 Security Considerations for refresh_token states:
The authorization server MUST verify the binding between the refresh token and client identity whenever the client identity can be authenticated. When client authentication is not possible, the authorization server SHOULD deploy other means to detect refresh token abuse.
For example, the authorization server could employ refresh token
rotation in which a new refresh token is issued with every access
token refresh response. The previous refresh token is invalidated but retained by the authorization server. If a refresh token is
compromised and subsequently used by both the attacker and the
legitimate client, one of them will present an invalidated refresh
token, which will inform the authorization server of the breach.
It can be concluded that if the authorization_server is able to verify the binding between a refresh_token
and the client to whom it was issued then refresh_token
can be used to obtain multiple access_token
and will never expire. else the authorization sever will invalidate the old refresh_token
and generate new refresh_token
with every access token refresh response.