Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

`config push` sets `external_email_enabled = false` when `[auth.email] enable_signup = false`, disabling password sign-in for all users

未关闭
#7,055 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
postgresql, typescript

调研方向

The bad mapping is the boolRow call at packages/config/src/project-config/registry-auth.ts:597, which ties [auth.email] enable_signup to external_email_enabled. Read the config schema parsing that rejects an enabled key under [auth.email], and the config push path that writes the auth config. Done means signup can be disabled without flipping external_email_enabled, with a test covering the config push mapping. The issue offers two fixes, so confirm the approach with a maintainer before writing code.

由索引模型根据 Issue 内容生成。

描述

🐛 Bug supabase/cli

Summary

Running supabase config push against a remote project whose config.toml has [auth.email] enable_signup = false sets the project's external_email_enabled to false. Email/password sign-in then fails for every user with 422 email_provider_disabled, while the CLI reports the auth config as updated / up to date.

Version

Reproduced on CLI 2.109.1 (2026-07-17). The mapping is still on main at 753520f (2026-10-06): packages/config/src/project-config/registry-auth.ts:597, boolRow(["auth","email","enable_signup"], "external_email_enabled"). Latest release checked: v2.120.0.

Steps to reproduce

  1. A remote project with the email provider enabled; email/password sign-in works.
  2. supabase/config.toml contains:
    [auth]
    enable_signup = false
    
    [auth.email]
    enable_signup = false
    
    The intent is no public self-signup: accounts are created by admins through the Admin API.
  3. supabase config push --project-ref <ref>
  4. POST /auth/v1/token?grant_type=password with valid credentials.

Expected

[auth.email] enable_signup = false disables email signup only. Existing users can still sign in, and external_email_enabled stays true.

Actual

external_email_enabled flips true -> false (read back from GET /v1/projects/{ref}/config/auth). Sign-in returns 422 email_provider_disabled for everyone. The CLI prints no warning.

No workaround in config.toml

Adding enabled = true under [auth.email] is rejected ('auth.email' has invalid keys: enabled), and that parse error also breaks supabase db push. So a project that wants signup disabled cannot use config push at all.

Recovery

curl -X PATCH https://api.supabase.com/v1/projects/<ref>/config/auth \
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" -H 'Content-Type: application/json' \
  -d '{"external_email_enabled": true}'

Related

  • supabase/supabase#40582 (open, no replies)
  • supabase/cli#4469 (closed unmerged)

Suggested fix

Do not map [auth.email] enable_signup onto the provider toggle external_email_enabled, or accept [auth.email] enabled in the schema so the provider can be kept on explicitly.

主要语言
TypeScript
星标
2.4k
派生
537
平均合并
21 小时 24 分钟
30 天内合并 PR
378

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

supabase/cli 的其他 Issue

查看 supabase/cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。