That would make sense

express.json simply uses bodyparser.json, so that would be it

Is it possible to have a different base URL for both SIgnup and Sign in while using

supertokens-node

? For example, I'd like APIs to be:

/users/login

-- Sign in API

/users

-- Signup API

You can’t change the default API. Path, but you can disable the default API and implement them by copying the source code from the node SDK In your own path

Okay cool, thanks.

Hello,is the api base path completely reserved with Supertokens. I have set my api base path in supertokens config as

/api

and also want my custom api's also to start with

/api

. Is that Possible??

Yes. That’s possible. Just create your custom APIs as usual, and as long as their path and method don’t collide with one of our APIs, it will work as expected

It isnt. I created my api as

/api/v1/users

which I dont believe collides. But am getting such an error

Right. You had opened an issue about this. I’ll have a look at it today.

Not only this, If my api just starts with

api

as the first three characters , the same error is shown. For example: /apia ,/apib etc

Sure thanks

This is really odd. Never happened before. So let me check

Sure ,no issues 😄

Can you try with setting the apiBasePath to “/api/auth”

And see if your custom API calls still fail like this

Just a sec

Now they are working fine

Okay! Thanks for the info. I’ll debug this today

Hey guys .... just came across SuperTokens ... just wondering if this use-case makes sense I mainly work with no-code apps. I am thinking of this very simple flow: i) User-authenticated: No-code app checks with Supertokens is user is validated. If yes proceed. If no, move to step 2 ii) If user not authenticated, move user to the magic login page Does this make sense?

Yea it does make sense. However, you would need to write code to integrate supertokens.

Thank you. Could you point me to the documentation section to the write the least amount of code implement this?

Start by selecting the login method you want to add https://supertokens.com/docs/guides

And then follow the quick setup guide for your stack

Hey, I had a quick question, could someone let me know the reason for double hashing the refresh token? Or point me to documentation about it? I'm just curious what the actual advantage of it was. Thanks!

hey @User you can see why here: https://github.com/supertokens/supertokens-core/issues/362

Perfect, thank you !

Anyone knows if its possible to use Supertokens with Azure AD? It seems it's possible to do it with ThirdParty login, but I am wondering if anyone has done it successfully before

It should be possible via custom Third party provider login. Here is something that works with active directory (if that's what you are looking for): https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/providers/activeDirectory.ts the reason it's commented out is cause it doesn't support multi tenant AD integration, but would work fine with just a single tenant. Is this what you were looking for?

Morning Is there a reason that the MySql tables config adds a

passwordless_users

table (https://supertokens.com/docs/passwordless/quick-setup/database-setup/mysql) but the PostgreSQL doesn't (https://supertokens.com/docs/passwordless/quick-setup/database-setup/postgresql)? Seems like

passwordless_users

is used by both implementations and not adding the table caused some errors in our implementation (but that could just be us)