@rp this is the hasura jwt config doc. https://hasura.io/docs/latest/graphql/core/auth/authentication/jwt.html#configuring-jwt-mode

if i solve the problem, i'd like to give a doc, because hasura+supertokens is very nice composition.

@User I am not entirely familiar with the hasura integration as of yet. I will check it out tomorrow most probably. But @User and his team were the one to make that integration in the first place 🙂 So perhaps he could answer your question.

Hey @User the authentication via JWT on Hasura won't work with supertokens unless you change some settings. We implemented using Webhook, which is a different setup: https://hasura.io/docs/latest/graphql/core/auth/authentication/webhook.html You will need ofc a webhook server for that, you can use our repository: https://github.com/offscriptio/hasura-supertokens to try it out. if you have questions let me know.

@User thank you, i will have a try~

@User @User https://github.com/offscriptio/hasura-supertokens/issues/24

I think we can discuss this issue again. I really want to connect hasura and supertoken in the most efficient way, so that we can write a lot less curd code😆

I will check later. We currently use webhook for every action in our case due our specific use case, we had problems with JWT rotation using other providers

@User hi, if hasura have much tables, each table need roles for access, what you do with this problem?

The authentication layer works for whole hasura, so if you have 1 or 1000 tables it doesn't change the issue. We have around 100 tables in our production environment and our webhook server runs in pretty low resources and footprint.

What I want to consult is that each table can specify the access rights of roles, which is a lot of work, if there are 100 tables.

message has been deleted

example: admin is inner role for root. add a test role. for every table, have to define permission for test, otherwise test role will have no right to query/insert... action

Ah, this is permission modelling on Hasura. This is something you'd have to do anyway no matter how you integrate. We never got this as a bottleneck as we are modelling and growing our product, we already model permissions on the go. This part of the workflow is manual itself. Or you can do on a yml file and push, but anyway, it's not automatic.

@User 😆 yeah, maybe we should do like you said, just one table by table as a CI way

This is something you only do once anyway: set up the roles permissions. So it's not a big issue after you have the first time it done.

yes, you are right~

and combine with the Inherited Roles, we can merge multi role to just one. for hasura not really use the allowed roles list for permission check.

@User how about you do the composition of roles ? use Inherited Roles ?

We are not using that for now. We have 4 different roles and a fallback role for logged in users without permissions. In the end we have role A, role B, role C, user and anonymous in our database.

i try the Inherited Roles, it works

@User thank your very much . i'm newbee to hasura. the webhook way providered by you can work well. and waitting @User to check/confirm the jwt logic with hasura jwt auth logic.

thank you @User !! You are very helpful :))

@User , I will get back to you tomorrow about this 🙂

@User you are very helpfull too👍

Hi there, is there any way to connect to the supertokens db through terminal? I just wanted to dump all the registered user data into a csv. I wasn't able to find anything in the documentation.

Are you using the managed service version?

I haven't hosted supertokens myself if that is what you mean.