Skip to content

[auth.sms] enable_confirmations opposite to supabase.com #4413

Closed as not planned

Description

@mfairley

Describe the bug
If you set

[auth.sms]
enable_confirmations = true

then sms confirmations will be disabled in the UI on supabase.com. Likewise, if you get it to false then it's enabled in the UI.

This is a potential security issue because you think confirmations are enabled but they are not.

To Reproduce
Steps to reproduce the behavior:

  1. Set enable_confirmations = true in config.toml
  2. Go to https://supabase.com/dashboard/project/<project_url>/auth/providers?provider=Phone
  3. Compare enable confirmation vs the config.toml file.
  4. I'm using Twillio Verify, not sure if the same problem exists for other providers

Expected behavior
config.toml and actual settings should match

Screenshots
Image

System information

  • Ticket ID: N/A

  • Version of OS: Darwin Michaels-MBP.lan 25.0.0 Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:26 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6041 arm64

  • Version of CLI: 2.54.11

  • Version of Docker: Docker version 28.5.1, build e180ab8

  • Versions of services: [output from supabase services command]

    SERVICE IMAGE | LOCAL | LINKED
    ------------------------|------------------------|------------
    supabase/postgres | 17.6.1.021 | 17.6.1.021
    supabase/gotrue | v2.182.1 | v2.182.1
    postgrest/postgrest | v13.0.5 | v13.0.5
    supabase/realtime | v2.41.23 | -
    supabase/storage-api | v1.26.3 | -
    supabase/edge-runtime | v1.68.3 | -
    supabase/studio | 2025.08.04-sha-6e99ca6 | -
    supabase/postgres-meta | v0.91.5 | -
    supabase/logflare | 1.18.3 | -
    supabase/supavisor | 2.6.1 | -

Additional context

Activity

  1. github-actions commented on Jun 17, 2026

    @github-actions
    Contributor

    Hi! Thanks for opening this issue.

    We're closing this because it has not had any activity for 45 days, and we try to keep the Supabase CLI issue tracker focused on reports that are still current.

    If this still reproduces on the latest Supabase CLI, please comment with /reopen on its own line and include your CLI version, updated reproduction steps, and any recent error output. We appreciate the signal and are happy to take another look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions