Allow signin without Email Verification

[dipeshhkc]

Hello Team. I have been using supabase for a week now and it is wonderful. Thank you for your hard work 🙇

I have a question. Please provide me with your suggestions on this.

I need to allow users to sign in even without email verification. I found Enable email confirmation setting and disable that option. But still I get Email Not Confirmed message during signin.

Is this intended? Or am I missing something?

[dipeshhkc]

It seems this doesn't work for the user-created from the server.
Is there any way to automatically verify the email or allow login without email verified for the user-created by the admin API?

[sadiki-o]

if u sign up a new user using the supabase.auth.signup() function u can pass confirmation_sent_at with a date so the new created user can signin, otherwise try to create a trigger whenever a new user is added to supabase the trigger after that update the new user row and set confirmation_sent_at to the current date which is now()

[WarrenBuffering]

Would we pass confirmation_sent_at along with the superbase.auth.signUp request? As part of the body's data property? Eg.

  const response = await supabase.auth.signUp({
    email,
    password,
    data: {
        confirmation_sent_at: Date.now(),
    },
  });

[WarrenBuffering]

A follow-up with more detail, though this is a patchy workaround and I'd rather not have to be using it.

Following this video, the function I created auto_confirm_account

begin
  NEW.email_confirmed_at = NOW();
  NEW.confirmed_at = NOW();
  RETURN NEW;
end;

Which I then set up a trigger auto_confirm_user which calls auto_confirm_account on INSERT for auth.users

[kiwicopple]

checking with the auth team now - I would have thought that the Enable email confirmation disabled would work for server-side updates. Will update again soon!

[kangmingtay]

hey @dipeshhkc, can you please email us at support with your project ref? Disabling "Enable email confirmations" shouldn't require you to still verify your email on sign-in so it might be a bug specific to your project.

[kangmingtay]

if u sign up a new user using the supabase.auth.signup() function u can pass confirmation_sent_at with a date so the new created user can signin, otherwise try to create a trigger whenever a new user is added to supabase the trigger after that update the new user row and set confirmation_sent_at to the current date which is now()

@sadiki-o can you elaborate more on how you were able to do this? AFAIK, the supabase.auth.signup() method doesn't support passing the confirmation_sent_at time

[rommyarb]

I've also experienced this when creating a user from the server using supabase.auth.api.createUser().
You can solve it by passing email_confirm attribute.

const createNewUser = await supabase.auth.api.createUser({
  email: 'me@mydomain.com',
  password: '123456',
  email_confirm: true,
})

[mike-luabase]

Is this fixed? I can't call supabase.auth.signUp without being forced to confirm the email.

[J0]

Hey @mike-luabase ,

Thanks for the query! You should be able to call supabase.auth.signUp without email confirmations enabled.

[J0]

Closing for ow but let us know if there are still issues