So our session management solution issues access tokens that are signed, but they aren't JWTs. So the only way you would want to verify the access token is via our backend SDK's

verifySession

function.

If you want a typical JWT, you will have to wait for 1-2 weeks. We will be releasing a feature which will issue you a standard JWT along with its JWKs endpoint (using which you can get the public key to verify the key).

Ah, ok! Thank you.

What's your use case at the moment? Are you not able to use our provided

verifySession

function?

I am using postgREST which allows you to use JWT claims to store role information that associates directly with database roles so you can get use Row Level Security on all app users. I may be able to get it to work another way though. Using verifySession seems easier anyways.

Ah I see. Interesting. Do you also have a separate backend / API layer?

in which you can write your custom backend logic

Yes

understood

So you have intergrated our backend SDK into your backend layer already?

And so your use case atm is that you want to query postgREST from the frontend directly using some JWT that we issue. Do I understand correctly?

Yes, that would be the use case.

alright! got it.

Our new realse very soon will solve for your use case 🙂

Incredible! Thank you

release*

Hi, question about the supertokens/supertokens-postgresql docker image: Is it possible to start with a delay? I have a docker-compose file and tried to set

command: sh -c "sleep 30 & supertokens start"

but the container continually restarts when calling with sh -c

Are you trying to make sure that the container is started after your db has started?

if yes, you can use the

depends_on

config: https://docs.docker.com/compose/startup-order/

I'm trying to wait for migrations, which happen in an init container. Depends does not work in this case, because migrations happen after the containter is started. This works though:

entrypoint: ["/bin/bash", "-c"]

command: "'sleep 30 && docker-entrypoint.sh supertokens start'"

ahh i see!

cool!

Hi, I'm new to supertokens and am following the Next.js docs to integrate it into an existing project. I've made it through steps 2 and 3, and I can view the login widget at /auth. However, I can't use email/pw or social signup or login, and I keep getting the error

Error: ThirdPartyEmailPassword recipe has already been initialised.

Any ideas what I might be doing wrong? (I can paste the full callstack if that's helpful.)

Hi! Steps 2 and 3 in which page?

Sorry, should have said pages 2 and 3. So, I've completed "3. Adding auth APIs" in the NextJS walkthrough

How about page 1? https://supertokens.io/docs/thirdpartyemailpassword/nextjs/init

Yes, I started there. I didn't start getting the build errors until completing steps 2 and 3.

(pages 2 and 3)

In the above page, step 6, "Call the init function", there is an error in the docs which hides the code snippet. Please click on "/pages/_app.js" tab to see it

did you complete that step too?