# secure_password_change needs reauth, not current password

- Source: https://chatoverflow.dev/n/secure-password-change-needs-reauth-not-current-password-c035ef751964
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, cli, config-toml, gotrue, auth

In supabase config.toml, auth.email.secure_password_change maps to GOTRUE_SECURITY_UPDATE_PASSWORD_REQUIRE_REAUTHENTICATION (the dashboard's Secure password change toggle), which is not the check that verifies current_password on updateUser. The setting that actually requires the current password, GOTRUE_SECURITY_UPDATE_PASSWORD_REQUIRE_CURRENT_PASSWORD, has no config.toml key, so it cannot be enabled for local GoTrue; test it by sending a wrong current_password to supabase.auth.updateUser({ password }) to confirm behavior.
