false alarm. I got it.

👍

Has anyone run into this issue?

< SuperTokens core threw an error for a POST request to path: '/recipe/session' with status code: 400 and message: Field name 'userDataInDatabase' is invalid in JSON input

I've managed to get everything else going - i.e. supertokens core running in a docker container

and i've updated my current user to allow connections to my local IP (192...) and the docker logs for the container show a successful connection to the db

as soon as i run this line to create the session, i get the error mentioned above:

await Session.createNewSession(res, user.ext_id, jwtPayload, null)

this is how i've imported Session:

const Session = require("supertokens-node/recipe/session");

Hey @tredstone instead of giving null, just give undefined as the last param

works! appreciate the help

If you want you can create an issue about this in supertokens-node repo to more gracefully handle null

Might be an opportunity for my first pr 🤔

Yea! Good idea

@User here is the issue if you wanna create a PR: https://github.com/supertokens/supertokens-node/issues/77

when the container is running correctly, what tables should be updating in the supertokens db?

currently i'm not seeing any records being added besides the 3 that are in the key_value table

the main motivation for this question is, i'm trying to support logout and I'm calling the

revokeAllSessionsForUser

method but it doesn't seem to be expiring the token calling another authenticated endpoint immediately after, doesn't seem to be triggering an error with Session.verifySession() middleware

is there a way to invalidate access tokens immediately?

> when the container is running correctly, what tables should be updating in the supertokens db? Depends on if you are using only sessions or sessions + login. On start, only the

key_value

table is updated.. as sessions are created, the

session_info

table is updated. As users are signed up, then

emailpassword_users

is updated and so on..

> the main motivation for this question is, i'm trying to support logout For logout, you need to mainly clear the tokens from the cookies on the frontend and need to revoke that user's session. This can be done using the

revokeSession

function after the verifying the session. Calling

revokeAllSessionsForUser

will only revoke the session from the db and not the cookies. This means that in case access token blacklisting is not on, the current access token in the cookie will continue to work, until it expires. To make access token expire immediately, please see https://supertokens.io/docs/emailpassword/advanced-users/advanced-session/access-token-blacklisting

Thank you

Is it possible to run an existing docker image with new config options?

Yea.

You need to pass it environment variables in the docker run command

Check out the the docker readme file we have

It’s there on our GitHub. A repo for the docker container. Based on the db you are using. The repo name is supertokens-docker-

so this seems to working in the sense that revoking the session and them following up with a request that requires a valid session with give a 401 however i still don't see any info updated in the superTokens db

When you revoke a session, it gets removed from the db

right now i'm just using the Session recipe when initializing the library, not sure if that is part of the cause

ah gotcha

Just using that should update the key_value and the session_info tables

i dunno why i thought the session invoke would remain in the db for history purposes