@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.

got it.

So ideally, you should create users by creating a node script that goes through your CSV file and calls the

signUp

function from the recipe you use

if that doesn' work for you, then we will have to manually do this for you.

> So ideally, you should create users by creating a node script that goes through your CSV file and calls the signUp function from the recipe you use Apologies, I don't think I was clear enough. I just wanted to get emails of all the users that have registered on my platform into a csv, and was figuring out if there is way to get that by connecting to my supertokens db directly.

Ahh.. since you are using the managed service version, we don't have that yet :(. We may allow that in the future, but not sure. That being said, we have pagination functions which allow you to loop through all users and do anything you'd like. Here are the docs for it: https://supertokens.io/recipe-redirect?to=/common-customizations/user-pagination&hide=session

Alright, so I will have to write the data I get into a file. I get it. Thank you. A little inconvenient I may say. I guess hosting supertokens on my own would be a good move as that would give me the ability to have a database of my own.

> A little inconvenient I may say. Yea fair enough.. What we can also do for now is to implement a feature where on the dashboard, we can allow you to export users as a csv file. Would that help?

Yep, that is what I was trying to find on my dashboard for a few minutes.

Cool. That should be done in 1-3 days from now 🙂

WIll ping you once it's done

Great! Thank you, looking forward to it.

Does supertokens not add cookies/session to requests made to the subdomain of the

apiDomain

?

Also, for some reason I am unable to get the userId in the backend in few requests? No cookies getting attached to the request.

@User > Does supertokens not add cookies/session to requests made to the subdomain of the apiDomain? You need to set the

cookieDomain

config in the backend's

Session.init()

to something like

".api.example.com"

. This will send the cookies to

api.example.com

and to

*.api.example.com

. I think there will be one more change required from our side for this to happen, which I can make today and release a new version... ------------- > No cookies getting attached to the request. - Is this the sub domain of your API's sub domain? Or is it a totally different API domain? - Have you correctly configured CORS for this domain? - Is this domain

https

, and is the

secure

flag in cookies

https

? - Is there any output on the browser console when querying this domain? - What is the status code output of the API when you query? 200? 401?

@User about your question: > Does supertokens not add cookies/session to requests made to the subdomain of the apiDomain? See our latest release (in the new-release channel), or https://supertokens.io/recipe-redirect?to=/common-customizations/sessions/multiple-api-endpoints

Thank you, I redirected the requests to the apiDomain. But this makes it easier for future. Apologies for the late reply. > - Is this the sub domain of your API's sub domain? Or is it a totally different API domain? This was for the apiDomain itself. > - Have you correctly configured CORS for this domain? The CORS is same for every requests, the cookies were getting attached to other requests but not these. I just imported Session in the component and obtained the userId in the frontend. Odd thing that happened was how just getting the userId in the component using

getUserId()

solved the issue. I didn't even use the userId in the request itself but the cookies started getting attached with the request. > Is this domain https, and is the secure flag in cookies https? Yes, https. > - Is there any output on the browser console when querying this domain? No there wasn't. I will check once again and let you know. > - What is the status code output of the API when you query? 200? 401? I was trying to obtain the userId in the backend and was returning an error status of 404 if the userId was null.

The problem was somehow solved, I would try to reproduce the above problem again and let you know what I find.

Okay! Sounds good.. there are many reasons why browsers may not send cookies, and it can be hard to know the exact reason.

Hey rp! I"m having issues with the sign out feature. It is supposed to nullify all the session cookies when its called?

Yes. It is supposed to do that