Cause the access token verification happens in the node js lib itself

Once the access token expires, u will need to call the refresh token, and then, it will try and call the service. Which is down

And then it will fail

But until then, ur access token will keep working. Since it’s a JWT

Cool!

Or, if u restart ur node process, things will stop working too. Since it gets the signing key from the service. Which is down

Btw what IDE do you use?

For java, IntelliJ

For JavaScript, VSCode

Ah, instead of postman I'm using Intellij HTTP client, it lets you write requests as code

So awesome

Ohhh. I didn’t know they have an HTTP client. Cool

so when I register, it automatically stores the cookie and anti-csrf

POST {{base_url}}/adminRegister
Content-Type: application/json

{
  "username": "admin1",
  "email": "admin1@email.com",
  "password": "password",
  "passwordConfirmation": "password",
  "userType": "admin"
}

> {%
 client.global.set('cookie', response.body.secureRoutes.cookie)
 client.global.set('anti-csrf', response.body.secureRoutes['anti-csrf'])
 client.global.set('refresh', response.body.refresh.cookie)
 %}

Sort of mimicking the front end SDK

That’s cool!

By the way, why do u haha response.body.refresh?

Have*

That is only for dev response, to do this exact thing

Ohhh I see

any other env it doesnt exist, neither does response.body.secureRoutes

I see

Also, if I drop table key_value is that bad? or will it regenerate?

It will regenerate, but all ur current sessions will be revoked

It will regenerate with a key values

But u must also restart the service at that point in time

I see!

started learning about docker and aws, so will user Supertokens docker image soon

Cool!

Hey RP, on the front end, how does the developer access the ID of the current user?

By calling an API to get user’s info