SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

jwks, get called very often. Is this normal? shouldn't the jwks get cached by the sdk?

Well, the client that’s calling the jwks endpoint from the backend SDK should be caching it. Not the backend SDK itself.

ah I found it 💀. It's the framework i use https://github.com/redwoodjs/redwood/blob/main/packages/auth-providers-api/src/supertokens/decoder.ts

quick questioin tho <@498057949541826571> . using the builtin function getAccessTokenPayload. Wont call the jwks right?

unknown

another quick question <@498057949541826571> 😄

does the supertokens keep refreshing the data in supertokens' database? This is a quick observation
- image 1 , supertokens' instance data transfer, indicating that it's really being used for the last 2 days. 
- image 2 and 3, is the supertokens's database usage. Indicating that it is very active

> does the supertokens keep refreshing the data in supertokens' database?
Well, most calls to the core require a database query.

yeah, I mean in this case, the core is not really being called (image 1). But the database resource is being used. Wondering if this is normal?

the core has a few cronjobs that run that require db access. It also has a connection pool that it maintains with open connections for quicker responses.

i see, got it. I am assuming the cron jobs, for example to maintain the google oauth2 refresh token etc?

oo i see, just searched the codebase. seems like deleteExpiredSession, deleteExpiredAccesstoken etc