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

オープン
#3,419 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
csharp

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
C#
スター
567
フォーク
107
平均マージ
1時間 19分
マージ済み PR(30日)
353

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fluentcms/FluentCMS のほかの issue

fluentcms/FluentCMS の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。