--- title: "1.42.5 — Packaged Admin confirms sensitive actions in place" description: "The packaged Admin moves to portal-mojo 0.2.28. When an action needs a recent sign-in, \"Confirm it's you\" now opens on the current screen and finishes the action you pressed, instead of sending you to the sign-in page. Browser clients on another origin can now read `Retry-After` on a rate-limited re…" date: "2026-11-10" tags: ["release"] canonical: "https://django-mojo.sitesmojo.com/changelog/1-42-5/" --- The packaged Admin moves to portal-mojo 0.2.28. When an action needs a recent sign-in, "Confirm it's you" now opens on the current screen and finishes the action you pressed, instead of sending you to the sign-in page. Browser clients on another origin can now read `Retry-After` on a rate-limited response. ### Changed - The packaged Admin at `/admin/v2/` is now portal-mojo 0.2.28 (was 0.2.22). - An action that returns HTTP 440 `reauth_required` opens a "Confirm it's you" modal over the current screen. It offers only what the account can use: passkey, password, and each active sign-in provider the deployment allows. - Provider and "Use the sign-in page" confirmation run the hosted sign-in page in a pop-up that reports back to the Admin tab. Confirming as the same account keeps the session, open dialogs and page state, and the pressed action finishes. Saves that carry a secret key ask for the key again. - Admin sign-out goes through the hosted signed-out landing, and Sign in can be retried after a canceled sign-out. - The Groups page opens for the global `manage_groups` permission, matching the server. - The Sign-in page lists every callback URL and domain for each provider. - Admin tables keep a selected preset filter when you press Clear all. - Stored Assistant messages show the tools they called. ### Fixed - Browser code on another origin can read `Retry-After` on a 429: it is now listed in `Access-Control-Expose-Headers`. - The Admin retries its realtime connection after a server authentication timeout. ### Upgrade notes - No migration and no new setting. The server behavior the new confirmation uses already ships. - Provider confirmation needs the browser to allow a pop-up for the site. A blocked pop-up shows a message in the modal, and password or passkey still work.