You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on an implementation which requires that after the user approved a client, the client needs to receive the refresh_token as well next to the access_token. I already implemented the refresh_token on the token route, meaning that retrieving a new access_token with a given refresh_token works. However, tokne.js doesn't seem to provide an input for a refresh_token.
What I expected is that one calls done(null, accessToken, refreshToken) and both get sent. How can this be implemented?
The text was updated successfully, but these errors were encountered:
Hey,
I am working on an implementation which requires that after the user approved a client, the client needs to receive the refresh_token as well next to the access_token. I already implemented the refresh_token on the token route, meaning that retrieving a new access_token with a given refresh_token works. However, tokne.js doesn't seem to provide an input for a refresh_token.
What I expected is that one calls done(null, accessToken, refreshToken) and both get sent. How can this be implemented?
The text was updated successfully, but these errors were encountered: