n1ru4l
10/18/2022, 2:02 PMrp
10/18/2022, 2:22 PMarth
10/18/2022, 2:27 PMarth
10/18/2022, 2:28 PMlamp-town-guy
10/18/2022, 10:42 PMChunkygoo
10/19/2022, 1:51 AMjin49
10/19/2022, 2:02 AMtyping_extensions==4.1.1
strictly required? or can we relax to >=4.1.1,<5.0.0
? I'm running into pip conflicts with other packagesnkshah2
10/19/2022, 5:11 AMnkshah2
10/19/2022, 5:28 AMexecreate
10/19/2022, 9:10 AMcreate_code_post / consume_code_post
function calls for Passwordless recipe, which makes it possible to get_session
using api_options.request
. But there is no such parameter for the Email-Password recipe 🥲execreate
10/19/2022, 10:19 AMcreate_new_session
call will get the user_id
from the latest recipe used in MFA flow, is that right? So how do I override the user_id
to contain the ID from the very first recipe in my MFA flow?execreate
10/19/2022, 11:29 AMn1ru4l
10/19/2022, 11:42 AMexecreate
10/19/2022, 1:40 PMJacobLUC
10/19/2022, 2:43 PMIaS1506
10/19/2022, 3:54 PMAlen
10/20/2022, 6:12 AMn1ru4l
10/20/2022, 7:19 AMdisableEmailPassword
option (passed to ThirdPartyEmailPasswordReact
from supertokens-auth-react/recipe/thirdpartyemailpassword
) for ThirdPartyEmailPasswordNode
(from supertokens-node/recipe/thirdpartyemailpassword
)?
If I only set disableEmailPassword
on the frontend it is technically still possible to sign up through the backend 🤔execreate
10/20/2022, 7:35 AMemail_verify_post
call take into account the user_id
in the session when verifying the token?mayankgopronto
10/20/2022, 8:17 AM404
response when using a chi
router. However it works just fine when I use net/http
.
Using this for reference: https://supertokens.com/docs/thirdpartyemailpassword/pre-built-ui/setup/backend#4-add-the-supertokens-apis--cors-setupAdiGutner
10/20/2022, 10:53 AMexecreate
10/20/2022, 1:34 PM2fa_completed_or_absent
. Everything is okay after I first log in, but after my access token expires (it is set to expire in 15 min) and I refresh my token there is a problem - I get this error from protected API endpoints:
json
{
"message": "invalid claim",
"claimValidationErrors": [
{
"id": "2fa_completed_or_absent",
"reason": {
"message": "wrong value",
"expectedValue": true,
"actualValue": false
}
}
]
}
When I try to decode the access token I can see that it contains the my custom claim and its value is correct:
json
{
"2fa_completed_or_absent": {
"v": true,
"t": 1666271203895
}
}
Do you think validation fails because of the timestamp? How do I avoid this?Copani
10/20/2022, 3:35 PMrp
10/20/2022, 4:39 PMeugene
10/20/2022, 8:50 PM/Users/eugenechan/Desktop/one-click-dao-builder/backend/node_modules/supertokens-node/lib/build/supertokens.js:347
.split(";")
^
TypeError: Cannot read properties of undefined (reading 'split')
has anyone faced this problem before?rp
10/21/2022, 3:17 AMxoldyckk
10/21/2022, 11:47 AMITEnthusiasm
10/21/2022, 6:02 PMpath
(from /auth/reset-password
to /reset-password
). Is that simple to do without messing anything up? 😅 It seems getResetPasswordUrl
is deprecated.Kaushik.K
10/23/2022, 6:41 AMMuerte
10/23/2022, 8:37 AM