So if you just move to "~2.1.0"

that should solve this issue.

Ohhh

Ok

🙂

🙂 Let me know if this error still persists.

Error was fixed

and now I have another one 😂

Error: No SuperTokens core available to query

Will dig around for this error.

Am I supposed to specify the port in the hosts?

@User you are to specify the host and port like this "http://localhost:3567" or "http://127.0.0.1:9000" Please make sure the docker container is reachable via some host and port on your machine. Alternatively, you can connect to "https://try.supertokens.io" to get started quickly. It's an instance of SuperTokens that we host for you for testing purposes

Oh do I need to allow http/https traffic?

Guess I messed up in that

you need to bind the host and port of the docker container to your machine. Once that is done, you can simply send a http request to the host and port you have bound the container to and it should work

Hey! We have made a demo app for those who want to see an example implementation of SuperTokens for NodeJS: https://github.com/supertokens/supertokens-demo-app

Hey @User I've got a problem where I'm using a third party service that needs to be secure. This is the situation: - I use SuperTokens to increase the Security of my app - I use a third party for a specific service. (I host the free server on AWS) - The third party uses refresh token based auth. - This means my app is now less secure because despite using supertokens, the most important part has tokens that are saved in async storage and they're just normal JWT How do I integrate the two?

So in this scenario, most such third party apps issue tokens so that you can talk to them. Many people use these tokens to also talk to their own backend (which is usually done in an insecure way). What you can do is continue using SuperTokens as you normally do, and save the JWT / refresh tokens provided by this third party service only on your backend. If these tokens are per user, then you can associate these tokens as JWTPayload or map them against userIds in your backend. This way, whenever you need to query this third party service, you verify the supertokens session (like you normally do), and the get the JWTPayload to get these tokens. Or from the userId, get these tokens. If you need these tokens on your frontend, you can save them localstorage and use those to query the third party service. If these tokens are compromised, then your APIs won't (cause your APIs don't use these tokens to give access).

@User please feel free to ask more questions if the above is not clear. I'm happy to get on a call as well to discuss this since it is a slightly complicated topic.

@User Sure, Ill be asking more soon. Ill think about how to best do this as it does seem complicated

👍

hi @User

Hi @User

Hey @User we talked before about external service im using that has it's own auth. I was having trouble with the service I was using so now I'm using a different service which is similar. This one lets you use your own Auth but this is what it says:

message has been deleted

How does one use this with SuperTokens?

So once a user logs in, what are the tokens this returns to your frontend?

Also, which OAuth flows does this support - authorisation code grant flow?

@User ^