While adding user to sessions during login , I want to pass the role manually through the body of request. How can I get hold of the value in the create-session function 🤔

While adding user to sessions during login , I want to pass the role manually through the body of request. How can I get hold of the value in the create-session function 🤔

third party email password

Oh . sounds like what I needed.

You should be able to get the body object for your framework by doing api_options.request.original

Thanks , found a way to solve the query. 😅

how did you solve it

used async , was getting an object reference everytime.

async api_options.request.json()

did it

you do you mean await?

ah yes , sorry

@User let's talk here

empty object {}

hmm. interesting

but there's something else too, during sign in , if I do the same exact thing, the context gets defined, so it's explicity for the sign up part

I see.

Thanks, would update the package then...

You should do that in the create_new_session function - since that's called during sign in too.

Ah got it, and would get the session details from the cache layers during verification.. thanks 👍

Yea. Makes sense. If you are OK with those info being accessible by the frontend, you can save it in access toke payload itslef.

Actually was planning to remove the usage of postgres for storing the session_details and put all of that on redis , for faster transactions.

Well, my point is that you can store that info in the access token itself. And that way you won't need extra db / cache to get it

Do you have any example where supertokens was used as a auth microservice ? Needed some reference for creating additionl api's

Im not sure what you mean. Can you elaborate?

I am exploring microservices and its different design patterns. In that, one of my microservice stands of to be Auth, which I wanted Supertokens to handle completely. There would be different api's which I would need to setup myself to handle sessions example In that, of session verification I would have a middleware , verifySession, which wont be present in the Other Microservices.

Uhmm. Not an example.

wdym by "other microservice auth" .

> "which wont be present in the Other Microservices." Your words. hehe

backend

right. So what you are asking for is machine to machine auth. We have limited support for that atm

The auth endpoints wont be exposed directly to the internet.

But, you can use our JWT recipe for it

hmmm, ig would need to change the flow of auth and make calls from frontend too..

> hmmm, ig would need to change the flow of auth and make calls from frontend too.. Well. You can continue to use sessions for calls from the frontend (that's the recommended way) For backend to backend, you can use JWTs, or have your own API keys, or put all the services in one private VPC.. or use another lib / solution for this.

Has the update rolled out?

yes. 0.6.0 version

Thanks, would check it out..

ok. So no breaking change for you

Thanks , it is working as expected. Also is there a wayto add columns to the databse and fill them dusing sign up through form _fields

You will need to add these columns to your own db

So the changes that would be required are: - add column to db - add the field in the form field during supertokens init

Yes.