Configuration

The way you want your users to authenticate can be driven via configuration.

If you open the global configuration at src/configuration.ts, you'll find the auth object:

import type { Provider } from '@supabase/gotrue-js/src/lib/types';

auth: {
requireEmailConfirmation: false,
providers: {
emailPassword: true,
phoneNumber: false,
emailLink: false,
oAuth: ['google'] as Provider[],
},
}

As you can see, the providers object can be configured to only display the auth methods we want to use.

1. For example, by setting both phoneNumber and emailLink to true, the authentication pages will display the Email Link authentication and the Phone Number authentication forms.
2. Instead, by setting emailPassword to false, we will remove the email/password form from the authentication and user profile pages.

Requiring Email Verification

This setting needs to match what you have set up in Supabase. If you require email confirmation before your users can sign in, you will have to flip the following flag in your configuration:

auth: {
requireEmailConfirmation: false,
}

When the flag is set to true, the user will not be redirected to the onboarding flow, but will instead see a successful alert asking them to confirm their email. After confirmation, they will be able to sign in.

When the flag is set to false, the application will redirect them directly to the onboarding flow.

Emails sent by Supabase

Supabase spins up an InBucket instance where all the emails are sent: this is where you can check the emails sent by Supabase when running locally.

To access the InBucket instance, you can go to the following URL: http://localhost:54324/.