What is the optimal deployment strategy for implem...
# support-questions-legacyv
vaz007.
06/29/2023, 12:21 PMWhat is the optimal deployment strategy for implementing a passwordless recipe with Lambda, considering the login needs of N users? Should we choose Lambda as the best option, or would an ECS and API Gateway structure be more suitable? Alternatively, are there any other strategies that offer better deployment options on AWS ?
r
rp_st
06/29/2023, 2:17 PMhey @vaz007. this is a personal choice really, but i don't like lambdas very much cause of the cold start problem.
v
vaz007.
07/04/2023, 6:34 AMexactly I was thinking of ECS and then I can forward the request to my authorization container, which then can forward request to an ELB
vaz007.
07/04/2023, 6:38 AMCan you tell me whats wrong with the following codebase
recipeList: [
Passwordless.init({
smsDelivery: {
override: (originalImplementation) => {
return {
...originalImplementation,
sendSms: async function ({
//codeLifetime, // amount of time the code is alive for (in MS)
phoneNumber,
//urlWithLinkCode, // magic link
userInputCode, // OTP
}) {
// TODO: create and send SMS
sdk.auth("APIKEY");
// const template =
Hello this is your OTP ${userInputCode} and link ${urlWithLinkCode}vaz007.
07/04/2023, 6:39 AMit says sendSms is not a valid operator for this API
vaz007.
07/04/2023, 6:39 AMoperation on this API
r
rp_st
07/04/2023, 6:39 AMcan i see the error stack?
v
vaz007.
07/04/2023, 6:40 AMjust a sec
vaz007.
07/04/2023, 6:40 AMError: Sorry,
sendSmsvaz007.
07/04/2023, 6:41 AMimport Passwordless from "supertokens-node/recipe/passwordless";
import Session from "supertokens-node/recipe/session";
import { TypeInput } from "supertokens-node/types";
import Dashboard from "supertokens-node/recipe/dashboard";
const sdk = require("api")("@msg91api/v5.0#6n91xmlhu4pcnz");
vaz007.
07/04/2023, 6:41 AMthese were my import statements
r
rp_st
07/04/2023, 6:42 AMi don't think this is from our SDK.
v
vaz007.
07/04/2023, 6:43 AMyeah missed it
vaz007.
07/04/2023, 6:44 AMsorry its from msg91
vaz007.
07/08/2023, 4:43 AMHey I am having a frontend post signup issue. Can you help me out ?
I am unable to call the onHandleEvent function
recipeList: [
Passwordless.init({
contactMethod: "EMAIL_OR_PHONE",
onHandleEvent: async (context: any) => {
console.log(context);
// let {id, email, phoneNumber} = context.user;
console.log(context.user);
if (context.action === "SUCCESS") {
if (context.action === "SESSION_ALREADY_EXISTS") {
// TODO:
console.log('SESSION ', context.action);
} else if (context.action === "PASSWORDLESS_RESTART_FLOW") {
// TODO:
console.log(context.action);
} else if (context.action === "PASSWORDLESS_CODE_SENT") {
// TODO:
console.log(context.action);
} else {
if (context.isNewUser) {
// TODO: Sign up
console.log(context.action);
console.log(context.isNewUser);
// await UserMetadata.updateUserMetadata('1', { role: "user" });
}
else {
// TODO: Sign in
console.log('SIGN IN ');
console.log(context.action);
}
}
}
},
}),
Session.init(),
]
r
rp_st
07/08/2023, 4:43 AMare you using custom UI or our pre built UI?
v
vaz007.
07/10/2023, 3:23 AMprebuilt
r
rp_st
07/10/2023, 5:25 AMdoes the
console.log(context);v
vaz007.
07/10/2023, 11:23 AMnope
r
rp_st
07/10/2023, 11:59 AMwhich login method are you using to sign up?
v
vaz007.
07/10/2023, 12:28 PMpasswordless
r
rp_st
07/10/2023, 12:29 PMare you manually calling the consumeCode function from our frontend sdk?
v
vaz007.
07/10/2023, 1:12 PMnope
vaz007.
07/10/2023, 1:12 PMI have just added onHandleEvent
r
rp_st
07/10/2023, 1:13 PMhmm. This is odd. Im tagging @porcellus who can help out here.
rp_st
07/10/2023, 1:13 PMhe may be able to help in the coming 2-3 days
v
vaz007.
07/10/2023, 1:13 PMCan't we just add metada on postSignup on backendSDK
r
rp_st
07/10/2023, 1:13 PMyou can. Yea
v
vaz007.
07/10/2023, 1:13 PMmetadata *
r
rp_st
07/10/2023, 1:13 PMit's there in our docs
rp_st
07/10/2023, 1:13 PMoverriding the consumeCode API
v
vaz007.
07/10/2023, 1:13 PMcan you point me to it
r
rp_st
07/10/2023, 1:14 PMhttps://supertokens.com/docs/passwordless/common-customizations/handling-signinup-success -> scroll to the second section
v
vaz007.
07/10/2023, 1:15 PMThanks let me give it a try
vaz007.
07/10/2023, 1:16 PMhmm just a question is supertokens planning to add authorization layer as well ?
r
rp_st
07/10/2023, 1:16 PMwe have RBAC already
v
vaz007.
07/10/2023, 1:17 PMimport UserRoles from "supertokens-node/recipe/userroles";
// creating the admin role and adding permissions to it.
await UserRoles.createNewRoleOrAddPermissions("admin", ["read:all", "delete:all", "edit:all"])
// creating the regular-user role and adding permissions to it.
await UserRoles.createNewRoleOrAddPermissions("regular-user", ["read:all", "delete:self", "edit:self"])
vaz007.
07/10/2023, 1:18 PMhow would you suggest to add API level RBAC in this
vaz007.
07/10/2023, 1:19 PMLooking at CASBIN for an alternative solution
r
rp_st
07/10/2023, 1:21 PMplease see our docs for this 🙂
rp_st
07/10/2023, 1:21 PMit's all in there.
p
porcellus
07/12/2023, 9:24 AMhi. This seems to be working as expected to me. If you need help with this could you add any other details that could help me reproduce this?
v
vaz007.
08/24/2023, 6:26 AMHey I need some help with supertokens. I have installed it locally on my MAC and when I hit localhost:3567/hello it works perfectly but when I hit it with my backend then it throws an error saying supertokens-core not found
export function getApiDomain() {
const apiPort = process.env.REACT_APP_API_PORT || 4001;
const apiUrl = process.env.REACT_APP_API_URL || `http://localhost:${apiPort}`;
return apiUrl;
}
export function getWebsiteDomain() {
const websitePort = process.env.REACT_APP_WEBSITE_PORT || 3000;
const websiteUrl =
process.env.REACT_APP_WEBSITE_URL || `http://localhost:${websitePort}`;
return websiteUrl;
}
export const SuperTokensConfig: TypeInput = {
supertokens: {
connectionURI: "http://localhost:3567",
apiKey: "someKey",
},
appInfo: {
appName: "Auth Middleware Express",
apiDomain: getApiDomain(), // ELB address
websiteDomain: getWebsiteDomain(), // Frontend ADDRESS IS MANDATORY DURING PROD
},
recipeList: [
Passwordless.init({
contactMethod: "PHONE",
flowType: "USER_INPUT_CODE"
}),
Session.init({
// cookieSecure: true, // over https since we are on local we can't switch this to true
}),
Dashboard.init(),
UserMetadata.init(),
],
vaz007.
08/24/2023, 6:29 AMand I am using prebuilt UI
r
rp_st
08/24/2023, 6:46 AMare you using docker?
v
vaz007.
08/24/2023, 6:47 AMhmm no I was using the core
r
rp_st
08/24/2023, 6:48 AMfor the node process, are you using docker?
v
vaz007.
08/24/2023, 6:48 AMno
r
rp_st
08/24/2023, 6:48 AMthen it's probably an issue with the firewall on your machine
v
vaz007.
08/28/2023, 7:18 AMHey I have deployed my frontend on S3 and backend on ECS, but for some reason I am facing CORS issue can you help me resolve the following issue
CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
vaz007.
08/28/2023, 7:22 AMshould I disable app.use(
cors({
origin: getWebsiteDomain(),
allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
methods: ["GET", "PUT", "POST", "DELETE"],
credentials: true,
})
);
part from the backend
r
rp_st
08/28/2023, 7:50 AMwhich API are you calling?
v
vaz007.
08/28/2023, 7:52 AM/auth/signup/code
vaz007.
08/28/2023, 7:52 AMusing supertokens 6.0
r
rp_st
08/28/2023, 7:56 AMhave you added the cors middleware before or after the supertokens middleware?
v
vaz007.
08/28/2023, 7:57 AMnope
vaz007.
08/28/2023, 7:58 AMnothing
vaz007.
08/28/2023, 7:58 AMdo you want me to share my backend file
r
rp_st
08/28/2023, 7:58 AMnot really
rp_st
08/28/2023, 7:58 AMyou just have to add the cors middleware befroe the supertokens middleware
rp_st
08/28/2023, 7:58 AMsee one of our example app;s
v
vaz007.
08/28/2023, 7:58 AMI am using your example app
vaz007.
08/28/2023, 7:59 AMboth on frontend and backend
r
rp_st
08/28/2023, 7:59 AMour example apps do work for surew
rp_st
08/28/2023, 7:59 AMmaybe you made some changes
rp_st
08/28/2023, 7:59 AManyway, i can't really help since you aren't ansering my question directly.
v
vaz007.
08/28/2023, 8:00 AMimport express from "express";
import supertokens from "supertokens-node";
import cors from "cors";
import { middleware, errorHandler } from "supertokens-node/framework/express";
import { getWebsiteDomain, SuperTokensConfig } from "./config";
import { authRouter } from "./routes/auth";
import {internalIPRouter} from './routes/internalIP';
import {authorisationUserRule} from './routes/authorisationUserRulesController';
const app = express();
// Initialize Supertokens with the provided configuration
supertokens.init(SuperTokensConfig);
// Set up Cross-Origin Resource Sharing (CORS) middleware
console.log('WEB DOMAIN : ',getWebsiteDomain());
app.use(
cors({
origin: getWebsiteDomain(),
allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
methods: ["GET", "PUT", "POST", "DELETE"],
credentials: true,
})
);
app.use(express.json());
// Supertokens middleware for handling sessions and related functionality
app.use(middleware());
app.get('/', (req, res) => {
res.status(200).send("HEALTH CHECK OK")
})
app.use("/auth", authRouter);
// app.use("/session", sessionRouter);
// app.use("/getUserMetadata", userMetadataRouter);
app.use("/internalIPAuth", internalIPRouter);
app.use("/authorisationUserRule", authorisationUserRule);
// Error handling middleware for Supertokens
app.use(errorHandler());
app.listen(4001, () => console.log(
API Server listening on port 4001vaz007.
08/28/2023, 8:00 AMhere is the file
r
rp_st
08/28/2023, 8:00 AMSeems about fine
rp_st
08/28/2023, 8:00 AMcors errors are out of scope of supertokens
rp_st
08/28/2023, 8:00 AMplease try to google them
v
vaz007.
08/28/2023, 8:00 AMyeah I am just not sure whats going wrong
vaz007.
08/28/2023, 8:00 AMthanks for your help
vaz007.
09/19/2023, 9:10 AMHey I have deployed my application. I just wanted to ask you can we deploy multiple frontends to contact with one backend ? Both frontend URLs will be different.
r
rp_st
09/19/2023, 11:55 AMYou can - can you descirbe the exact use case here?
v
vaz007.
09/19/2023, 1:27 PMyeah so we are using multiple recipies on backend which includes Passwordless for one platform, and Email & Password for the other platform. So backend remains consistent.
We need to specify our website domain in the backend and frontend according to the examples in the website
vaz007.
09/19/2023, 1:27 PMso I was not sure on how to tackle this situation
r
rp_st
09/19/2023, 1:45 PMare the frontend domains on different sub domains or entirely different domains? Also, will the backend apiDOmain value be same for both the websites?
rp_st
09/19/2023, 1:45 PMit would be great if you can give the actual domains for the websites and the backend, so i can tell u exactly what you need to do
v
vaz007.
09/21/2023, 6:21 AMHey sorry for delayed response we are on same doamin and different subdomain. I just have one additional question, in supertokens version 14 I am able to generate email verification tokens but I am unable to generate a link. So how does the process work and I don't want to upgrade it to supertokens 15 since I would need to go and change all my existing APIs
r
rp_st
09/21/2023, 6:22 AMu can form your own link from the token
rp_st
09/21/2023, 6:22 AMjust add the token as a query param to the link manually
rp_st
09/21/2023, 6:22 AMsee the existing link structure and pattern match
v
vaz007.
09/21/2023, 6:23 AMohh okay cool
vaz007.
09/21/2023, 6:25 AMthanks
vaz007.
09/21/2023, 6:26 AMwas just little confused on creating link part. Thanks for all your help we are finally running passwordless recipie on dev env and planning to integrate thirdparty as well
5 Views