Skip to content

A1 Shell and sign-in #3152

Open
Open

Description

@pournasserian

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:

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

Activity

  1. added
    type:epicMilestone-level feature, sliced into issues
    area:adminThe Blazor WebAssembly admin and the admin halves of plugins
    on Nov 15, 2026
  2. pournasserian commented on Nov 16, 2026

    @pournasserian
    MemberAuthor

    To do when main is next brought into feature/a1 after #3199 (#3198) has merged: the decision record docs/decisions/0007-admin-sign-in-flow.md says 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/revoke that 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:adminThe Blazor WebAssembly admin and the admin halves of pluginstype:epicMilestone-level feature, sliced into issues

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions