GWGSo, I built a simple refresh token implementation, but the refresh tokens aren't tied to the access tokens, so the only way a refresh token gets removed is if it expires or is redeemed. Seems wrong
jamietannaGWG I don't have them tied currently (nor have revocation) but I'm planning on having a "consent ID" that'll be in both tokens, and be what can be used to revoke both tokens by the user
Loqijamietanna: GWG left you a message 5 hours, 36 minutes ago: When you have a few minutes, would you be able to act as a sounding board for refresh token implementation?
GWGSo, if I redeem a refresh token, I should invalidate the old refresh token, which is fine, but should I also invalidate the access tokens associated with that refresh token, or just let them expire naturally?
aaronpki would say it makes sense to revoke the access token immediately too. since only one client should be using the access token, if that client uses the refresh token then it should never be using the previous access token again
aaronpkthe only exception is clients that are made up of multiple parts (threads, processes, etc) where they may not be able to coordinate between all the parts