Add support for test email OTPs

Open
#901 5 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
authentication

Research direction

The issue does not name files, tests, or entry points. Start by locating the email OTP and auth-user creation flows, then determine how dashboard-configured email and OTP pairs should affect sessions; done means the configured test path logs in without sending an email and is covered by tests.

Written by the indexing model from the issue text.

Description

enhancement

Feature request

I'm currently using sign-in with email but sending the user an OTP.
For testing, app submissions, and end-to-end tests, I would love a feature where we could specify an email and OTP combination in the dashboard that would log you in without actually sending you an email.
When creating this pair, an auth user with that email would also be created for handling sessions.

This would be great for app submissions and UI testing for folks that have OTP as their only login method (like me).

Dominant language
Go
Stars
2.6k
Forks
764
Avg merge
5d 3h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/auth

All issues in supabase/auth

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.