Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

config push: changing auth.oauth_server.authorization_url_path fails with 400 (enabled and path must be sent together)

Abierto Apto para principiantes
  • ¿Algo no está bien?
#7,087 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
76/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
supabase, typescript
Área
backend, cli

Línea de trabajo

Lee apps/cli/src/commands/config/push/push.encoders.ts en torno a las entradas del servidor OAuth y compáralas con los grupos que deben ir juntos para captcha, SMTP o auth hooks. Reproduce el push que solo cambia la ruta del issue y luego comprueba que el cuerpo de la solicitud codificada incluya el valor enabled actual junto con la ruta modificada. La tarea está terminada cuando la actualización se realiza correctamente sin desactivar el servidor OAuth; verifica también el caso inverso en el que solo cambia enabled.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

🐛 Bug supabase/cli

Follow-up to #6367, which was closed as completed. On the new TypeScript CLI the diff half is fixed, but the push half still cannot change authorization_url_path on a project where the OAuth server is already enabled: the plan is correct, the request is rejected with a 400.

Version

supabase@next = 3.0.0-next.4 (via npx), Windows 11. Hosted project with oauth_server_enabled = true and oauth_server_authorization_path = "/oauth/consent".

Reproduce

supabase/config.toml, nothing else declared:

project_id = "<ref>"

[auth.oauth_server]
enabled = true
authorization_url_path = "/.lovable/oauth/consent"

supabase config push --project-ref <ref> --yes
Actual
Updating Auth service with config:
auth.oauth_server.authorization_url_path [update]
  local:  "/.lovable/oauth/consent"
  remote: "/oauth/consent"

HTTP PATCH: https://api.supabase.com/v1/projects/<ref>/config/auth
ConfigPushAuthUpdateStatusError: unexpected status 400:
{"message":"Both OAUTH_SERVER_ENABLED and OAUTH_SERVER_AUTHORIZATION_PATH must be provided together when updating OAuth configuration"}

Nothing is written. config diff afterwards still reports the same update.

Expected

The path is updated. enabled is declared in the file and equals the remote value, so it is (correctly) not a change, but the Management API wants it in the same body as the path.

Likely cause

config push is diff-first and sends only changed fields. In apps/cli/src/commands/config/push/push.encoders.ts the three auth.oauth_server.* entries are plain scalar rows (source), not a required-together group like captcha, SMTP or the auth hooks, where an unchanged member is sent along with its current value. So a path-only change produces a body with oauth_server_authorization_path and no oauth_server_enabled.

Treating oauth_server_enabled + oauth_server_authorization_path as a required-together group should fix it. I have not checked whether the reverse case (changing only enabled) is rejected the same way; the error message suggests it is.

Why it matters

There is no CLI workaround that keeps the server up: the only way to make enabled part of the diff is to flip it, which takes the OAuth server down. On our project this path resets to /oauth/consent on its own from time to time (described in #6367), so being able to pin it from config.toml is the whole point.

Minor, related: with only authorization_url_path declared (no enabled = true), config diff lists the path under unmanaged and compares nothing. That follows ADR 0022, but the message does not say that declaring enabled = true is what makes it comparable.

Happy to test a build against a live project.

Lenguaje dominante
TypeScript
Estrellas
2.4k
Forks
533
Merge medio
1 d 5 h
PR fusionados (30 d)
338

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de supabase/cli

Todos los issues de supabase/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.