We already store the RUID inside the database's Session table. When a request to invalidate occurs, we ask JWTSessions::Session to locate the refresh token by RUID and invalidate it. We could at the same time effectively expire/destroy the associated access token as the refresh token maintains a reference to the access token.
If that doesn't work, we could store both the RUID (refresh) & UID (access) in our Sessions table.
Will not fix as we have proven in issue #10 that this is unnecessary as the moment we invalidate the refresh token found at RUID the access token it is paired with is immediately rejected.
We already store the
RUID
inside the database'sSession
table. When a request to invalidate occurs, we askJWTSessions::Session
to locate the refresh token byRUID
and invalidate it. We could at the same time effectively expire/destroy the associated access token as the refresh token maintains a reference to the access token.If that doesn't work, we could store both the
RUID
(refresh) &UID
(access) in ourSessions
table.Check out https://github.com/tuwukee/jwt_sessions#flush-sessions in the jwt_sessions gem.