From fecac320d94070c70e13d9c35809adc19a280f0c Mon Sep 17 00:00:00 2001 From: Cristian Felipe Cruz Buitron Date: Sat, 29 Aug 2026 16:03:40 +0000 Subject: [PATCH] feat(commerce-backend): habilitar login con Google via Medusa auth module Agrega el modulo @medusajs/medusa/auth con providers emailpass (explicito, para no perder el default al customizar el modulo) y google, leyendo GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET/GOOGLE_CALLBACK_URL desde commerce-secrets con required(). --- workloads/commerce-backend/medusa-config.ts | 24 +++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/workloads/commerce-backend/medusa-config.ts b/workloads/commerce-backend/medusa-config.ts index f6863e7..3454364 100644 --- a/workloads/commerce-backend/medusa-config.ts +++ b/workloads/commerce-backend/medusa-config.ts @@ -157,6 +157,30 @@ module.exports = defineConfig({ ], }, }, + { + resolve: "@medusajs/medusa/auth", + options: { + providers: [ + // emailpass se declara explicito junto con google -- una vez + // que el modulo auth se customiza, la doc no deja claro si el + // provider default (emailpass) se sigue registrando solo. + { + resolve: "@medusajs/medusa/auth-emailpass", + id: "emailpass", + options: {}, + }, + { + resolve: "@medusajs/medusa/auth-google", + id: "google", + options: { + clientId: required("GOOGLE_CLIENT_ID"), + clientSecret: required("GOOGLE_CLIENT_SECRET"), + callbackUrl: required("GOOGLE_CALLBACK_URL"), + }, + }, + ], + }, + }, ], // ADR 0006 Etapa 2. Sin required(): a diferencia de S3/DB, Meilisearch