Unfortunately this event will be at 3am in my time zone, so a little difficult to attend. But the question I would like to ask is when this issue will be fixed:
When using a Pre-registration action, e.g. to validate the user’s email, after we set the access to deny (api.access.deny(‘deny_reason’) , the passwordless universal login proceeds showing the user an input field to enter the OTP code and a button to resend the code (although it correctly doesn’t send the OTP email/sms).
I know this is a known issue , but i’m wondering if a) the Auth0 team will release a fix soon and b) whether anyone has a workaround to continue using passwordless + email-va…
Problem statement
When using New Universal Login with Identifier First and SMS passwordless connection, if a pre-user-registration action blocks access with api.access.deny(), the action triggers but the login page shows no error to the user, and the flow continues asking for the sms code, as if it was successful. The same occurs with passwordless email login attempts.
Solution
This is a known issue that the Auth0 engineering team intends to address. However, the timing of the fix release has …
It’s very confusing to our customers to get an error at the same time as being told a verification code has been sent.
1 Like