It worked, thanks

awesome!

is it possible to update a session and change and already set value instead of only adding new ones?

@User yes. The session object has an updateAccessTokenPayload function which takes the new payload JSON. https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/sessions/update-jwt-payload

Hey there! 🙂 I wanted to ask what the proper way of doing the following is. Some users are already logged in via Third Party Auth. (Goole) Now I'd like to add user roles to grant admins access to some functions. I implemented the code on client side and am setting a 'admin' role in the "createNewSession: async function (input) { ..." method on the NodeJS server side. The issue: This is only called when logging in from a fresh start. I need to set the access roles even for the users already logged in. It seems that "refreshSession" is not called somehow, so what would be the proper place to add this to get set for users who are already logged in? I feel its one of those methods I should intercept, but dunno which. https://supertokens.com/docs/fastapi/api-reference/session-dependency Would be super glad about help. 🙂 And btw.: Supertokens is really really nice, I love it!

What version of the backend / frontend SDKs are you using? > It seems that "refreshSession" is not called somehow That's odd. Do you mean existing sessions are not being refreshed at all after their access token expires? The session has an updateAccessTokenPayload function using which you can change a user's current session's payload. So you would set up an API which is called from the frontend to do this. This would only happen when the user uses the app though. If you want to add the roles in an offline manner, you should loop through all the sessions for the relevant user, and then call the updateAccessTokenPayload on those sessions with the new role. Then when their session is refreshed, their access token will reflect the new role.

> Supertokens is really really nice, I love it! Thanks :))

Thanks for the fast response! I'll dig into it a bit more right now and will look at the updateAccessTokenPayload a little more! 🙂

Cool! Please feel free to ask more questions 🙂

Hello, I'm a newbie!! 😄 I'm currently setting up SuperTokens on my NextJS project. I've only gone through Step #2 where it tells me to visit /auth and see the Login UI andn if not come here at discord. So I'm mainly followed all instructions inculding this 😅 But I'm not seeing the Login UI, anyone else had encountered the same issue??

Hey! Can you show us the code snippet that you have added to your project?

Which part? The instructions asked me to create different JS files.

The configs that you have added, and the part that auth/[[...path]].js file too

And which recipe are you using?

And the frontend config please?

I just copied these in the instructions and removed some providers from the original code

Hmm. Do you see anything in the console log of the browser when you visit http://localhost:3000/auth?

its looping POST and GET calls. It doesnt stop unless I move away from the URL

where did you add the auth/[[...path]].js file?

Does this work? Where is this fetching from?

This should be in:

pages
├── auth
│   └── [[...path]].js

Oooh my mistake. I'll try again

For frontend setup, you can't add in the api folder. The API stuff is in the next steps..

It worked!! my bad

great :))

Is this recipe hosted by SuperTokens? Is there a recipe for self-hosting?

All recipes can be self hosted.

Please have a look at the architecture diagram for more details on how it's setup: https://supertokens.com/docs/community/architecture Essentially, you have to run a micro service (what we call "supertokens core"), which connects to your database. This service can be self hosted, or can be managed by us.