trev
03/04/2022, 9:32 PMazzlack
03/07/2022, 8:31 AMrp
03/07/2022, 8:36 AMNathanSkoot
03/07/2022, 11:38 AMpasswordless_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)rp
03/07/2022, 11:40 AMrp
03/07/2022, 11:40 AMNathanSkoot
03/07/2022, 11:40 AMrp
03/07/2022, 11:44 AMCREATE TABLE IF NOT EXISTS passwordless_users (
user_id CHAR(36) NOT NULL,
email VARCHAR(256) CONSTRAINT passwordless_users_email_key UNIQUE,
phone_number VARCHAR(256) CONSTRAINT passwordless_users_phone_number_key UNIQUE,
time_joined BIGINT UNSIGNED NOT NULL,
CONSTRAINT passwordless_users_pkey PRIMARY KEY (user_id)
);
rp
03/07/2022, 12:52 PMteebot
03/07/2022, 12:54 PMteebot
03/07/2022, 12:55 PMrp
03/07/2022, 1:19 PMgetUserByPhoneNumber
(https://supertokens.com/docs/nodejs/modules/recipe_passwordless.html#getUserByPhoneNumber).
- Loop through all users using our user pagination functions and filter the ones you want to take action on.
- Download the user CSV file from the dashboard and filter the ones in there to find the right user.teebot
03/07/2022, 2:07 PMteebot
03/07/2022, 3:09 PMoverride: {
apis...
consumeCodePOST
I was thinking of revoking all sessions for the user before creating a new one. + communicating to the user that a new login attempt happened if revokeAllSessionsForUser
returns at least one existing handle.
does it sound good to you @User ?rp
03/07/2022, 3:14 PMteebot
03/07/2022, 3:16 PMteebot
03/07/2022, 3:16 PMrp
03/07/2022, 3:17 PMteebot
03/07/2022, 3:19 PMteebot
03/07/2022, 3:19 PMrp
03/07/2022, 3:19 PMteebot
03/07/2022, 3:19 PMuser
03/07/2022, 5:27 PMrp
03/07/2022, 5:28 PMuser
03/07/2022, 5:29 PMuser
03/07/2022, 5:30 PMrp
03/07/2022, 5:30 PMrp
03/07/2022, 5:31 PMuser
03/07/2022, 5:33 PMButtonPusher
03/09/2022, 12:05 AM