supertokens-node
supertokens-node copied to clipboard
supertokens
Node SDK for SuperTokens core
Most of the tenant not found cases in core returns 400. Which is not handled in the SDK and the SDK ends up throwing 500. This behaviour must be changed...
Currently, when an unimplemented recipeId (rid) is passed in the header, the middleware doesn't handle the request. It results in a generic 404 error, providing limited information. Proposal: Enhance the...
Context: AWS Lamdba has a node servlerless SuperTokens middleware: Ref: https://supertokens.com/docs/thirdpartyemailpassword/serverless/with-aws-lambda/auth-serverless Request to have a similar node serverless middleware for Azure Functions (Microsoft Azure's AWS Lambda equivalent)?
So using a custom SMTP setting will break the SDK in edge functions.
Currently when using `origin` as a function in SuperTokens.init, the base request and user context are passed in the input. The function should also receive the tenant id in the...
We need to verify/fix our compatibility with the latest (4.X) fastify versions. The lib depends on types from an outdated (prev major version) fastify.
**Issue:** In the process of upgrading from V14 to V15 of SuperTokens Node and integrating Apple Sign In, it was found that the absence of the `redirectURIOnProviderDashboard` parameter in the...
The default API implementation for Apple redirect post includes the following code: ``` options.res.setHeader("Location", urlObj.toString(), false); options.res.setStatusCode(303); options.res.sendHTMLResponse(""); ``` This way of redirecting does not work with Fastify (tested on...
if not passed, makeDefaultUserContext, else add default values into the userContext that was passed