Should old OAuth 2.0 refresh tokens be revoked -
in principle, should existing oauth 2.0 refresh tokens (for given client/user combination) revoked when new refresh token issued following password grant authentication?
i can't find specific in spec. legitimate reissue same refresh token subsequent password logins?
the oauth spec section-6 specifies that:
the authorization server may issue new refresh token, in case client must discard old refresh token , replace new refresh token. authorization server may revoke old refresh token after issuing new refresh token client. if new refresh token issued, refresh token scope must identical of refresh token included client in request.
so there no requirement must issue new refresh token , revoke old one, however, same reason access_tokens expire idea issue new ones. compromised refresh_token valid until subsequent refresh. allow developer revoke refresh token should ever leaked.
Comments
Post a Comment