Arreglar callback de Authentik
All checks were successful
build-and-deploy / build-and-deploy (push) Successful in 23s

Problema: El callback /outpost.goauthentik.io/callback estaba en el router
público sin middleware de Authentik, causando que llegara directamente
a Node.js → 404 Error

Solución: Quitar /outpost.goauthentik.io del router público para que
el callback pase por el router principal con el middleware
authentik-forward-auth@file, que maneja correctamente el flujo OAuth
This commit is contained in:
2025-10-27 15:49:38 -06:00
parent 1ea50f0aa5
commit ac850620ba

View File

@@ -36,8 +36,9 @@
- "traefik.http.services.wifi-nucleoriofrio-service.loadbalancer.responseforwarding.flushinterval=1ms"
- "traefik.http.services.wifi-nucleoriofrio-service.loadbalancer.serverstransport=wifi-transport@file"
# Router 1: Público (assets, manifest, icons, callback de Authentik) - SIN autenticación - ALTA PRIORIDAD
- "traefik.http.routers.wifi-nucleoriofrio-public.rule=Host(`wifi.nucleoriofrio.com`) && (PathPrefix(`/assets`) || PathPrefix(`/.well-known`) || PathPrefix(`/icons`) || PathPrefix(`/outpost.goauthentik.io`) || Path(`/manifest.webmanifest`) || Path(`/favicon.ico`) || Path(`/vite.svg`) || Path(`/sw.js`))"
# Router 1: Público (assets, manifest, icons) - SIN autenticación - ALTA PRIORIDAD
# NOTA: /outpost.goauthentik.io NO debe estar aquí, lo maneja el middleware de Authentik
- "traefik.http.routers.wifi-nucleoriofrio-public.rule=Host(`wifi.nucleoriofrio.com`) && (PathPrefix(`/assets`) || PathPrefix(`/.well-known`) || PathPrefix(`/icons`) || Path(`/manifest.webmanifest`) || Path(`/favicon.ico`) || Path(`/vite.svg`) || Path(`/sw.js`))"
- "traefik.http.routers.wifi-nucleoriofrio-public.entrypoints=websecure"
- "traefik.http.routers.wifi-nucleoriofrio-public.tls.certresolver=letsencrypt"
- "traefik.http.routers.wifi-nucleoriofrio-public.service=wifi-nucleoriofrio-service"