Repository navigation
Description
Tracking issue for milestone A1 of the admin plan. Goal: an editor signs in to the admin of the reference image.
Exit criteria: from the reference image on SQLite, an editor signs in at /admin through the hosted login with PKCE, sees the sidebar of the types it may read in each of its sites, switches site, stays signed in across a token refresh in each of two tabs, enrols in two-factor, and signs out; a session that ends keeps the unsaved form.
Suggested order, in three lanes:
- Before the milestone, beside A0: Give the admin the caller's access, the locales of its sites and its preferences #3096, the caller's access, the locales of its sites and its preferences. It touches the backend only, its route names are settled in that issue, and A-08 cannot start without it; its pull request goes into
maindirectly. - Lane A: A-07, the sign-in flow, then A-09, the account page.
- Lane B: A-10, the hosting package and the reference host at
/admin, then A-11, the end-to-end harness, which needs both A-10 and A-07. - Lane C: A-08, the shell, once Give the admin the caller's access, the locales of its sites and its preferences #3096 and A-07 are merged.
The maintainer's part: none. The reference image in CI runs on localhost; FluentCms:PublicOrigin is configuration of a deployment.
Branch: the issues are worked on feature/a1, cut from main after feature/a0 is merged. Each issue opens its pull request into it, and one pull request from feature/a1 into main closes them after full CI. Bugs go to main.
CI and waiting: an issue pull request runs the fast checks only; enable auto-merge on it as soon as its review is done. The browser tests of A-11 run in full CI only, with the browser cached between runs. Run the manual full CI on feature/a1 once after A-07 and A-10 are merged, not only before the final pull request. ci.yml and feature-ci.yml already cancel a superseded run of the same branch.
Dependencies: Microsoft.Playwright 1.64.1 (A-11); a QR code encoder for the authenticator URI in A-09, QRCoder or the admin's own, named with its version in that issue before it is added. No issue adds a GitHub Action.
Decision records: A-07 records why the sign-in flow is the admin's own (AQ2).
Design: docs/planning/admin-technical-spec.md, sections 2.4, 4.1, 4.3, 6.1, 6.4, 7, 9 and 10.2.
Issues
- Give the admin the caller's access, the locales of its sites and its preferences #3096 Give the admin the caller's access, the locales of its sites and its preferences (gap of the audit, backend)
- Sign-in of the admin with the code flow and PKCE, refresh, sign-out, and expiry with the draft kept #3145 Sign-in of the admin with the code flow and PKCE, refresh, sign-out, and expiry with the draft kept (A-07)
- Admin shell: layout, sidebar, site switcher, user menu, breadcrumbs, themes, tablet layout #3146 Admin shell: layout, sidebar, site switcher, user menu, breadcrumbs, themes, tablet layout (A-08)
- Account page of the admin: sessions, two-factor, external logins, password change link #3147 Account page of the admin: sessions, two-factor, external logins, password change link (A-09)
- FluentCMS.Admin.Hosting and the admin of the reference host at /admin, with the client registration and the local loop #3148
FluentCMS.Admin.Hostingand the admin of the reference host at/admin, with the client registration and the local loop (A-10) - End-to-end harness of the admin on the reference host, with sign-in through the hosted page #3149 End-to-end harness of the admin on the reference host, with sign-in through the hosted page (A-11)
Activity
Approve the admin specification and plan A0 and A1 (#3153)
pournasserian commentedon Nov 16, 2026
To do when
mainis next brought intofeature/a1after #3199 (#3198) has merged: the decision recorddocs/decisions/0007-admin-sign-in-flow.mdsays that an unconfirmed logout leaves the server session alive and that a revocation cut off at sign-out leaves the refresh token valid. Once end-session revokes the session's authorizations, replace those sentences with: "A logout the user does not confirm leaves the server session and its tokens alive; a confirmed logout ends the server session and revokes every authorization issued in it, with its refresh and access tokens (#3198), so a revocation at/connect/revokethat is cut off or fails at sign-out no longer leaves the refresh token redeemable once the logout completes; what remains is a sign-in from before #3198, whose cookie carries no session id, and the consent of a third-party client, which a logout does not end." Check the sentence against the merged code before writing it.Bring main into feature/a1 and record what a confirmed logout ends (#…