pluto
PLUTO-429
/a-solucionar: landing page for non-allowlisted users who attempt login — explains issue, prompts email update. All roles, all projects.
Done normal
unassigned
⛔ awaiting elazar
Questions
Route naming: is /a-solucionar the public blocked-email landing (user-facing), or the admin irregularities dashboard (auth-required)? Venus ships /solicitar-acceso for blocked emails; mars/pluto have /a-solucionar as admin dashboard. Which is correct for pluto?
Two routes: /solicitar-acceso = public blocked-email landing; /a-solucionar = admin irregularities dashboard (auth-required). Ratified by Elazar -30391/-30393, confirmed mars+venus. WI#409 renamed to /solicitar-acceso.
Activity
-
wi cli
-
Spec: public route /a-solucionar. Triggered from auth/callback when isAllowlistedEmail() returns false — redirect /a-solucionar?reason=email-not-allowed. Page: no auth required, shows brief Spanish explanation ('Tu cuenta usa un email no permitido') + allowed domains list + instruction to contact admin or re-register with allowed email. No DB query. Per-project allowed-domain list via NEXT_PUBLIC_ALLOWED_EMAIL_DOMAINS env (comma-sep) or hardcoded fallback. Cross-project: pluto, mars, venus each implement independently once spec ratified. WI#409 blocks on evolutiva-commons §Auth ratification.
-
q#23 to=elazar: Route naming: is /a-solucionar the public blocked-email landing (user-facing), or the admin irregularities dashboard (auth-required)? Venus ships /solicitar-acceso for blocked emails; mars/pluto have
-
awaiting elazar
-
q#23: Two routes: /solicitar-acceso = public blocked-email landing; /a-solucionar = admin irregularities dashboard (auth-required). Ratified by Elazar -30391/-30393, confirmed mars+venus. WI#409 renamed to
-
Title correction: this WI is for /solicitar-acceso (public blocked-email landing), not /a-solucionar (which is the admin irregularities dashboard). Ratified per Elazar -30391/-30393 + 3-PM consensus.
-
completed
task
2026-05-17
6w ago
2026-05-17 20:45