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
What's the idea behind those two? I expected to get a token and a refresh token as result of the tokenAuth mutation and that I need to use the refresh token with the refreshToken mutation in order to receive a new pair of tokens!?
Can you please bring some light into this?
Also I wonder how to logout a user? Simply delete the token on the client side?
The text was updated successfully, but these errors were encountered:
By default, you receive a token that is not stored in DB and is used as a refresh token as you have mentioned above
2nd option is to enable long-running refresh token in settings after enabling that you will receive refreshToken in tokenAuth mutation that is stored in DB which and can be revoked prematurely using revokeToken mutation
If I use the
authToken
mutation as explained in the README.jwt_schema
defines :If I login, I receive this:
refresh_token
andpayload
are always null ....In an attempt to refresh the token, I tried the
refreshToken
mutation and passed my current token, which worked and got me this response:Again,
refresh_token
is null as wellWhat's the idea behind those two? I expected to get a token and a refresh token as result of the
tokenAuth
mutation and that I need to use the refresh token with therefreshToken
mutation in order to receive a new pair of tokens!?Can you please bring some light into this?
Also I wonder how to logout a user? Simply delete the token on the client side?
The text was updated successfully, but these errors were encountered: