---
title: "1.12.1 — Automatic hosted authentication for Edge WebApps"
description: "django-mojo 1.12.1 makes same-origin MojoAuth routing part of every Edge-hosted WebApp, preserves SPA sign-in callbacks, and automatically repairs existing WebApp vhosts during Edge startup."
date: "2026-08-18"
tags: ["release"]
canonical: "https://django-mojo.sitesmojo.com/changelog/1-12-1/"
---

django-mojo 1.12.1 makes same-origin MojoAuth routing part of every Edge-hosted WebApp, preserves SPA sign-in callbacks, and automatically repairs existing WebApp vhosts during Edge startup.

### Added

- Edge-hosted WebApps now receive MojoAuth login, registration, passkey, and supporting authentication API routes automatically during onboarding.
- Existing hosted WebApps are reconciled automatically when Edge job engines restart after an upgrade.
- Operators can repair only a WebApp's authentication routes without rotating its deployment credentials.

### Fixed

- The bouncer decoys `/login`, `/signin`, and `/signup` are now exact routes, preserving application paths such as `/signin/login` and `/signin/callback`.
- Same-origin bouncer assessment requests no longer fall through to static WebApp hosting and return nginx 405 responses, preventing authentication challenge loops.

### Upgrade notes

- Pools with more than one eligible API upstream must set `EDGE_WEBAPP_AUTH_UPSTREAM`; unambiguous existing authentication routes and single-upstream pools are discovered automatically.