im currently trying to setup custom claims in jwt ...
# support-questions-legacy
n
im currently trying to setup custom claims in jwt . i can see that the accessTokenPayload has changed after calling mergeIntoAccessTokenPayload but the actual jwt seems to be unaffected
r
hey @nosmaster89 are you using the node SDK? If yes, this bug has been solved in the latest version of the SDK - please update to it.
n
man you guys are on fire . thanks for the reply that worked just fine
no scratch that its still not updating in the actuall jwt . i was looking at the access token still
r
Can you check the actual version you got?
In package-lock
n
"version": "12.1.0",
r
Make sure to remove that file and remove node modules and update
Right. That’s the latest
Can you logout and login again and see if it works?
n
hand on package lock says 12.0.5
r
Haha yea. That’s before the bug fix
n
updated(lock says 12.1.0) logged out and in still cant see the updated jwt
r
Hmmmm. Are you sure? We have a test for this and it passes
n
fixed . 1 line of eronious code in my api causing it to no update the token (thought i was at fault not a bug) , works flawlesly after a update 🦾
r
Ok nice
n
before i continue down this hole . theres no supertokens plugin for mosquitto ?
r
I’m not sure. Iv never heard of that
n
its a mqtt broker . i need my frontend to connect to it and issue topic rules dynamicly. i have found a plugin that supports jwt as password that can allow custom rules passed into via the jwt
r
I see. You could add custom claims to JWT in supertokens and then send that JWT to the broker. That should work
n
thats the plan yes . i was hoping for some native ST intergration as there are some plugins that do postgres/mysql authentication
r
Hmmm. Yea. That’s not there at the moment.
2 Views