Skip to content

Account page of the admin: sessions, two-factor, external logins, password change link #3147

Open

Description

@pournasserian

Problem

Rows 4.2 and 4.16 give a user its sessions with revoke and two-factor enrolment by choice, and the routes exist under /me. The admin has no page where a user manages itself.

Proposal

An account page under /account with:

  • Sessions from GET /me/sessions, ending one with DELETE /me/sessions/{id}.
  • Two-factor: status from GET /me/two-factor; enrol with POST /me/two-factor/enrol, showing the authenticator URI as a QR code drawn in the browser, then /verify; recovery codes; disable.
  • External logins from GET /me/logins, removing one with DELETE /me/logins/{provider}.
  • A link to the hosted /account/change-password, opened in the same tab.
  • Interface language and theme, kept in the browser until PUT /me/preferences of Give the admin the caller's access, the locales of its sites and its preferences #3096 exists, then there.
  • A key or a service account cannot sign in to the admin; the page handles the 403 of the two-factor and logins routes if ever reached.

Dependencies: a QR code encoder for the authenticator URI. QRCoder (MIT) at its current stable version, named here before it is added, unless a small encoder of the admin's own is cheaper; no JavaScript is added.

Acceptance

  • As an editor on the test host: sessions listed, one ended; enrolment completed with a code from the shown secret, recovery codes shown once, two-factor disabled again
  • An external login is listed and removed
  • The password change link opens the hosted page and returns to the admin
  • Language and theme choices persist in the browser
  • Component tests cover the page with a fake API; the API tests cover the routes it calls

Design: docs/planning/admin-technical-spec.md, sections 4.3 and 10.2 (A-09). Size: S.

Activity

  1. pournasserian commented on Nov 16, 2026

    @pournasserian
    MemberAuthor

    Note from the review of #3189 (#3145, the sign-in), for this issue: sign-out revokes only the refresh token, so the authorization and the access token live on until they expire, and the session stays listed. Consider ending the session with DELETE /me/sessions/{id} at sign-out, and show on this page which session is the current one.

  2. pournasserian commented on Nov 16, 2026

    @pournasserian
    MemberAuthor

    Note from the review of #3199 (#3198), for this issue: a session in GET /me/sessions is one authorization, and a browser session can hold several (one per tab that went through the authorize endpoint). DELETE /me/sessions/{id} revokes that one authorization and leaves the browser's sign-in cookie alive, so the tab signs in again silently and gets new tokens. Since #3198 each authorization issued in a browser session is marked with that session's id, so this page can list and end by server session: one row per browser, and ending it ends every authorization of that session; say on the page what ending a session does and does not end (the cookie of another browser cannot be deleted from here; it stops working at its next request to the authorization server only if the server refuses it). Check what is on feature/a1 when this is built, since #3198 lands on main first.

  3. pournasserian commented on Nov 16, 2026

    @pournasserian
    MemberAuthor

    Decisions taken while building the page, conservative where the specification leaves the point open:

    • Language and theme. GET/PUT /me/preferences exist on feature/a1, but the preferences hold no theme, so the theme stays the shell's, in the browser (spec 4.1). The language is saved as the culture of PUT /me/preferences (the other members sent back as read), which is the source. The start does not apply it yet: a browser copy for the first paint has to be read before the host starts, which needs an interop type outside the allow-list. With English the only shipped culture (AQ14) nothing can differ, so that waits for the second culture.
    • Sessions. GET /me/sessions does not say which row is the current one, so none is marked. The page says that ending a session stops that sign-in at its next request and does not sign the browser out of the authorization server. Ending this tab's session makes the next read a 401, and the session's normal path signs in again. Once End-session does not revoke the session's authorization, so a refresh token outlives a sign-out #3198 is on feature/a1, the list can go by server session.
    • QR code. The admin has its own encoder (byte mode, level M, versions 1 to 15), not QRCoder: QRCoder 1.8.1 (MIT) brings System.Drawing.Common on net6.0 and up, which is a second package, and its net6.0 assembly is 204 KB before trimming.
    • Password link. The hosted page returns only to a local URL, so ReturnUrl is sent only when the admin is on the authority's origin, as in the reference host. On another origin the page returns to its own host.
  4. added a commit that references this issue on Nov 16, 2026
    9a1410a
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:featureNew capability

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions