Thanks!

I am having some setting up supertokens using docker. In the section, where it says localhost/127.0.0.1 is not applicable for mysql host, what should be the correct value? I have setup mysql locally on 127.0.0.1, should i put my own ip address?

Yes, your own IP address.

So you will also have to make sure that MySQL is listening on that IP address AND that the user you create can do operations if connected to via IP address (there are many tutorials online for this)

Alright thanks!

Also, setting up without docker, I am receiving following error Starting task: DeleteExpiredAccessTokenSigningKeys Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/catalina/LifecycleException Wondering if it is a common issue?

Can you tell me the steps you ran and which OS?

I am using Ubuntu 20 LTS I downloaded the core file, installed and entered "supertokens start" It does create tables in the database but runs into this error immediately.

Huh.. interesting. Can you please open a github issue about this? I'll have a look at it today / tomorrow.

Sure

Thanks. You can open it here: https://github.com/supertokens/supertokens-core/issues

I have tried it out, but still the only thing I am getting in input is userId, accessTokenPayload remains empty, and I need access to things like e-mail etc. Since u said that querying database is not the right approach, how can I achieve that?

Can you share some code regarding how you tried to set the content in the access token payload?

Also, querying the db is fine. What I meant is that sending the user ID to the backend to identify the user is not fine.

Oh okay misunderstood then 😄 I wasn't even trying to set the content as createNewSession(input) has only userId on it, but that might be an issue with creating access token payload service now when I am thinking about it 🙂

but the way u suggested with setting the keys and retrieving it works fine (tested on static data) 🙂 I just needed to access dynamic data from db, and thought that's wrong until now 🙂 Thanks for clearing it out for me! 🙂

Awesome! You can run any logic (even async logic) in the

createNewSession

function. So accessing the db and then putting that info in the access token payload should work! Btw, when is the info in the db inserted? In the post sign up override or somewhere else?

Is anyone here interested in helping me figure out adding ssl to my supertokens server? I'm trying to use the superTokens docs

The docs has a guide on how to do that

I'm using the ST docs

Ah ok

Hi, why in the install with docker there is a license? Why do we need a license if it's open?

hey @User we follow the Apache 2.0 license (which is an open source license). The license you see in the install dir is exactly that one.

And why do we need a license when installing with docker?

We just put it in there cause that's standard practice.

You don't actually need any license key or anything

Are you talking about something else?

Go to your dashboard to get the docker image and license key ID

About this