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
{{ message }}
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.
Hi,
it would be great if server could issue new token with new data - new expiration or session-like data. Now i couldn't do either, token have to expire by itself and then can be issued and session-like data can be saved in connection object, but are lost after connection and reconnection.
The text was updated successfully, but these errors were encountered:
@Mangatt You can always make a request using a valid token and it will return a new one, albeit with the same data and expiration, unless you setup a before hook on the auth/token service to alter the JWT payload.
We have some fixes coming in the 0.8 branch that will make it easier to issue tokens with different options and different payloads.
or providing whatever custom JWT options you would like:
constoptions={secret: 'your secret',jwt: {// your custom options. See https://github.com/auth0/node-jsonwebtoken}};app.passport.createJWT(payload,options)
So it is entirely up to you when you would like to do it.
Hi,
it would be great if server could issue new token with new data - new expiration or session-like data. Now i couldn't do either, token have to expire by itself and then can be issued and session-like data can be saved in connection object, but are lost after connection and reconnection.
The text was updated successfully, but these errors were encountered: