Users and invitations pages of the admin (A-31)

Aperta
#3,419 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp

Direzione di ricerca

Start with sections 4.15 and 10.7 of docs/planning/admin-technical-spec.md, then trace the administration assembly and Management API routes for /users and /invitations. Check the referenced dependency issues #3378, #3391, and A-51 before beginning. Done means both pages meet the listed access, role, session, invitation, keyboard, localization, component-test, API-test, and end-to-end acceptance criteria.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:admin type:feature

Problem

Rows 3.16 and 4.2 ask that an administrator manages the admin users from the admin. The Management API has /users and /invitations, and the admin has no page for either: inviting a user, changing its roles or ending its sessions takes the CLI or a direct call.

Proposal

Pages /users and /users/{id} in the administration assembly (4.15), for a caller who holds users.manage for the instance:

  • The list, read in pages, with search by name and address, and each user's state: active or deactivated, locked out until, two-factor on, must change the password.
  • The detail: roles added and removed, deactivate and reactivate, the sessions with revoke, the external logins with remove, the two-factor reset and the forced password change.
  • Invitations: send with roles, the pending list, revoke.
  • Refusals are shown by what they mean: a change needs every grant of the target's roles, and sending or revoking an invitation every grant of its roles (FCMS3103); the last active Super Admin (FCMS3052); a two-factor reset by a caller who did not sign in with a second factor (FCMS3064), with the way to sign in again with one.
  • What the API does not give is shown as it is. lockoutEnd is read-only, since no route ends a lockout. A user's answer does not say whether it has a password, so the forced password change is offered with a note that it needs one, until #3378 settles it. The pending list may hold an invitation whose sender no longer stands, until #3391.

Acceptance

  • An administrator finds a user by search, adds and removes a role, deactivates and reactivates it, ends one of its sessions, removes an external login and resets its two-factor
  • An invitation is sent with roles, shows as pending and is revoked
  • A caller below the target's roles sees the refusal named, and the last Super Admin cannot be deactivated or lose its role, with the reason shown
  • A caller who holds users.manage through a site role only sees no entry and no page
  • The pages are usable by keyboard alone, and no text is hard-coded
  • Component tests cover the list, the detail and the refusals; the API tests check each record against the OpenAPI document; an end-to-end case invites a user and changes the roles of another

Design: docs/planning/admin-technical-spec.md, sections 4.15 and 10.7 (A-31). Rows 3.16, 4.2. Needs A-51. Size: M.

Lingua principale
C#
Stelle
567
Fork
107
Merge medio
1h 19m
PR unite (30g)
353

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fluentcms/FluentCMS

Tutte le issue di fluentcms/FluentCMS

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.