app works, I get login page, let me just check if I can login in successfully

I'll create github issue right away

thanks

thanks

@User create issue https://github.com/supertokens/supertokens-node/issues/240 also added a comment as I found a potential temporary work around (built successfully). Just need to test locally that it still works ok.

thanks! will have a look

Hey @User I was trying to access the doc today. I was unable to access it before because of some issues. But it seems you have made it private. Is there any chance to view it again?

Ah yea. One sec.

Just the first four pages.

Lmk if this is helpful or not 🙂

Got it! Thanks a lot.

Hi! I'm currently trying to integrate SuperTokens with NestJS, yet I do wonder what I might have missed. I made all the steps described, though none of them seemed to actually add any routes to my application that could've been used for authentication. Based on the demo app, it would've been something like

/auth/signin

. On top of that I'm using GraphQL by default, which obviously wouldn't really interfere, still, the error filter applies to that part of the application as well. The main problem is that the

errorHandler

expects

next

(

NextFunction

to be passed in as the 4th argument, yet NestJS/`apollo-server-express` does not seem to expose that. When inspecting what the result of

ctx.getNext()

, it appears to be a normal context object, containing the

request

etc.

The routes are added via our middleware: https://supertokens.io/docs/thirdpartyemailpassword/nestjs/guide#4-exposing-supertokens-apis-using-its-middleware

> yet NestJS/apollo-server-express does not seem to expose that. hmmm.. interesting.

Have you already had any issues with that/anybody integrating with the same tech stack?

people have used nestJS with nextJS and graphql with nextJS. But using all three is rare. I can't recall anyone with that that has asked questions on this server.

I've briefly looked into the source code, and at first glance it didn't seem to do anything extraordinary. Could it be a solution to just write my own error filter?

The errorHandler is useful for catching errors thrown by our SDK function which are called in your APIs (in your case graphql queries)

session related errors. Nothing else

In fact, you could just not add it.. and things will work fine

it's there as sort of an optimisation really.

Yes, I'm aware what they are supposed to do, but if all they do is mapping the "internal" errors to some nicer error objects, then I can simply roll my own error message and return that one/do the mapping myself.

They send a 401 to the client if you used a function that reads from an expired session in your APIs

if you don't add those, instead of a 401, it will send a 500 which will display an error in the UI. But then when the user tries to call the API again, this time the session verification will fail which will return a 401 to the frontend and all will be as expected.

actually, you can just give it some empty function as the next handler since it won't be called anyway. Cause you are filtering based on

STError

anyway.

I kind of see it then. My initial assumption was that it's only responsible for mapping it for my GraphQL API, that's why I said that then I can do it myself as well. But if the frontend SDK actually relies on its functionality, I can simply throw my own fancy error for the GraphQL part, and if the

next

is present (which should be the case for the normal REST endpoints), then I can use the original functionality.

Cool! Lmk if you run into any issues.

Hi. I was trying to sign-up with LinkedIn using the "custom providers" method. I checked the docs (https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/signup-form/custom-providers) and also checked other third party providers (https://github.com/supertokens/supertokens-node/tree/master/lib/ts/recipe/thirdparty/providers). But always ended up getting a 403 error. Anyone succeeded in doing with LinkedIn?

Hey @teja can you send your backend implementation code? Will be easier to debug