The spec doesn't seem to have any recommendations on this point, but should an 
OAuth v2 API always return the same access token if the same client makes 
multiple requests? Is there any benefit to not generating a new access token 
for each request? Similarly, if you do generate new access tokens (as I am 
doing now), should you also generate new refresh tokens?

An unrelated question about revoking access tokens when the same authorization 
code is used more than once: should refresh tokens also be revoked? And, if so, 
should any tokens issued with that refresh token then also be revoked? It seems 
simpler (if slightly less correct) to just revoke all access tokens for that 
specific client/resource pair in that case, rather than tracking the ancestry 
of all tokens.

Thanks,
Ross

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to