Prevent user to be added on Dashboard if rules throw error

[jimzer]

Hello,

I have trouble understanding the user creation process.
I have a whitelist rule that call an API to get a list of authorized email address. In the rule, if the user email is not present in the whitelist I call the callback with an error:
return callback(new UnauthorizedError(‘Access denied.’));

However even though the login is canceled with the error, the user is still showing up in the Dashboard users list.
How can I prevent the user to be added to my users if the login is denied?

Thanks

[dan.woda]

Hi @jimzer,

Welcome to the Community!

You should be able to accomplish this with a pre-registration hook.

Check out this thread:

How to restrict sign ups for certain users

We have a scenario where we need to restrict the sign up to the specific types of users. We use lock v11. Currently, the signup flow is as follows: User signs up using the form. The new user is created in the default database of the auth0. We run some rules regarding register action and send a verification email. But we have a scenario where we need to restrict sign up access to specific users. Following are the approaches we tried: We tried using the “signup submit” event to perform certa…

[jimzer]

Thank you.
Would it work with social login ?
Because we use only Google sign in for now. If the pre-registration hook can work for first social logins it would be perfect

[dan.woda]

Ah no I missed that detail, this will not work with social. Social users don’t register, per se. They are only logging in, since they already have registrations with google. You can block them via a rule, or you could probably even delete the user in a rule and return unauthorized…I haven’t seen this done but that doesn’t mean it isn’t possible. I might have time to test it this week.