603466164219281420 #general

so we allow you to specify the claims on creation of a new session. The parameter in the createNewSession function is called jwtPayload -> which is a map/object.

10/11/2019, 2:47 PM

by default, that is empty = no user claims

LucaCastelnuovo

10/11/2019, 2:47 PM

What are the default claims used by the library?

10/11/2019, 2:48 PM

sessionHandle
userId
refreshTokenHash1
expiryTime
parentRefreshTokenHash1
antiCsrfToken
userPayload (the claims you pass)

LucaCastelnuovo

10/11/2019, 2:49 PM

thank you

10/11/2019, 2:49 PM

ur welcome

10/25/2019, 6:28 AM

Hello! To get free implementation support, schedule a call with us on https://calendly.com/supertokens-rishabh.

nkshah2

11/15/2019, 10:53 AM

DISBOARD: The Public Server List Hi! I am a bot for DISBOARD (https://disboard.org/) 🤖 COMMAND LIST !d help: This! !d bump: Bump this server !d page: Get server page link !d invite [channel]: Change Instant Invite to this channel. If [channel] is specified, create Instant Invite for that channel (Admin only)

11/15/2019, 10:54 AM

!d bump

nkshah2

11/15/2019, 10:54 AM

!d bump

tredstone

11/20/2019, 4:12 PM

i'm looking to use this library for our project but i had a couple of questions. our application will allow users to purchase items. We have a some endpoints that require authentication (placing orders, logging in, logging out, changing profile and settings info) and others that done (view available products, view product details) i was thinking of have one axios/supertoken instance to handle the endpoints that require authentication, and another axios for the non-secured endpoints on the backend, would i be able to wrap a small set of endpoints that require authentication and leave out the others?

11/20/2019, 4:17 PM

You can use the same axios instance for APIs that require authentication and for the ones that don’t. But if you want to use different instances, that works perfectly fine too. Now to actually answer your question, on the backend, you can apply SuperTokens to a subset of APIs quite easily. Are you using node? @tredstone

tredstone

11/20/2019, 4:22 PM

yes, and express

tredstone

11/20/2019, 4:22 PM

i'm curios to know more about using a single axios instance on the front end though. i'm going to pull the demo app shortly and take a look at what's going on as well

11/20/2019, 4:23 PM

So with express, you have two ways to use it - with a middleware and without a middleware.

11/20/2019, 4:24 PM

If ur using a middleware, you can apply the middleware to certain APIs only (the ones that require authentication). This will allow ur other APIs to be unaffected.

11/20/2019, 4:24 PM

If your not using middleware, then for the APIs that do not require authentication, u can simple not use any of the SuperTokens functions in it.

tredstone

11/20/2019, 4:25 PM

makes sense

11/20/2019, 4:27 PM

Using a single axios instance throughout your frontend would work the exact same way as you would normally use it - except that you have to call SuperTokensRequest.makeSuper(axios) whenever (and immediately after) you import an instance of axios.

11/20/2019, 4:28 PM

I hope this answers your question. If not, please feel free to ask more

tredstone

11/20/2019, 4:34 PM

oh i see, call SuperTokensRequest.makeSuper(axios) and use the instance returned from this for the requests that require authentication? i quickly went through the docs once (today when i found the project) so my appologies if the questions sounds basic.

11/20/2019, 4:36 PM

That function returns nothing. All you have to do is call it. And then continue using axios as u would regularly. See this page (with interceptors section) for an example: https://supertokens.github.io/supertokens-website/docs/axios/sending-requests

11/20/2019, 4:37 PM

And of course, you also need to call the init function of the library as shown in the link above.