Roles of the admin: list, editor and grants from the permission catalogue, with the site's Public role (A-32)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- csharp
- Área
- backend-api-design, frontend
Línea de trabajo
Read sections 4.15 and 10.7 of docs/planning/admin-technical-spec.md, then trace the administration assembly and its existing Management API integration. The proposal names /roles, /roles/{id}, GET /permissions, GET /plugins, GET /me/access, and the PUT save flow; use these to locate the relevant entry points and component and API tests. Done means the acceptance cases pass, including grant constraints, site scoping, Public role behavior, and refusal handling.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
Rows 3.16, 4.3 to 4.8 and 8.14 ask that roles and their grants are edited in the admin, the permissions of plugins among them, and row 4.8 that the public access of a site is set there. The Management API has /roles and GET /permissions, and the admin has no page for them.
Proposal
Pages /roles and /roles/{id} in the administration assembly (4.15):
- The list of the roles the caller may manage:
roles.managefor the instance shows every role, and in a site that site's roles. The server answers the whole list, so the page filters what it read. - The editor: name, description, site,
requireTwoFactorand the grants. - A grant picks a permission or a pattern from the catalogue of
GET /permissions, grouped by itssource(core, content, plugin, settings), with the plugin behind a permission fromcontributions.permissionsofGET /plugins(row 8.14). - The editor marks what the caller does not hold, from
GET /me/access, and the server stays the authority: its 403FCMS3103names the role and is shown on it. - A save replaces every grant of the role (
PUT). So the editor sends back each constraint of a grant as it read it,resourcesamong them, although it does not edit them: constraints are A-52's, and until then they show read-only on their grant. - A role has no
ETag. A concurrent change answersFCMS3045; the editor says so and reads the role again without dropping what the user typed. - The site's Public role is edited in the same editor, under a notice that its grants are what anyone reads without signing in (row 4.8).
- Refusals by their code: a built-in role changed or deleted (
FCMS3043), a role still held (FCMS3044), the last active Super Admin (FCMS3052).
Acceptance
- An administrator makes a role with grants of core, of a content type and of a plugin, changes it and deletes it
- A role with constrained grants is saved with its name changed and keeps every constraint,
resourcesincluded - A grant the caller does not hold is marked, and the server's refusal is shown on the role
- The Public role of the site is edited under its notice, and what it grants is read without signing in
- A caller who holds
roles.managein one site sees and changes that site's roles only - Component tests cover the catalogue, the round trip of constraints and the refusals; the API tests check the records against the OpenAPI document; an end-to-end case makes a role and gives it to a user
Design: docs/planning/admin-technical-spec.md, sections 4.15 and 10.7 (A-32). Rows 3.16, 4.3 to 4.8, 8.14. Needs A-51. Split when A6 was planned: the constraints of a grant are A-52. Size: M.
- Lenguaje dominante
- C#
- Estrellas
- 567
- Forks
- 107
- Merge medio
- 1 h 19 min
- PR fusionados (30 d)
- 353
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de fluentcms/FluentCMS
-
area:localization plugin type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area:storage type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
area:testing type:bug
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
area:api area:publishing type:feature
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
fluentcms/FluentCMS#3473 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:storage plugin type:bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de fluentcms/FluentCMS
Issues similares
-
worldInstancedOccluderNode reads its appendix count as one byte, but it is a VLQPosiblemente ocupada @spuddeh la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimePosiblemente ocupada @Goldziher la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
priority:P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
lompotc silently drops Java/C# class members past 128 instead of erroring, as its header claimsAbiertobug sev-5 vm
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100