API keys page of the admin, with a secret shown once (A-33)

Abierto
#3,421 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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

Línea de trabajo

Read docs/planning/admin-technical-spec.md sections 4.15 and 10.7, plus the referenced requirements in rows 3.1, 3.3, 3.16, and 4.9. Trace the Management API /api-keys and the administration assembly, then check the dependency on A-51 before starting. Done means the listed key operations, one-time secret handling, permission refusals, component and API tests, and end-to-end case meet the acceptance criteria.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:admin type:feature

Problem

Rows 3.16 and 4.9 ask that API keys are made and managed in the admin. The Management API has /api-keys, and the admin has no page for it. Nothing in the admin can show a secret once and copy it either: the wrapped set has no such component, and no clipboard type is on the script allow-list.

Proposal

A page /api-keys in the administration assembly (4.15):

  • The list of the keys the caller may manage: apikeys.manage for the instance shows every key, and in a site the keys bound to its sites. Any other key answers 404, which the page shows as not found.
  • Create with class, role, sites, types, expiry, rate limit and allowed addresses. The server checks the permission before it checks that the role and the sites exist, so a caller without it gets the refusal and no field errors.
  • The secret is shown once, with a copy button, and is not kept by the admin: a component of FluentCMS.Admin.Components and a clipboard type on the allow-list of 3.1 and 3.3, which the webhooks and MCP halves use after it.
  • Rotate with an overlap, from none to the server's longest; expire, which only moves the expiry forward; revoke; the allowed addresses.
  • Refusals by what they mean: rotate, revoke, expire and the allowed addresses need every grant of the key's role as bound (FCMS3103).

Acceptance

  • An administrator makes a key for one site and one role, copies its secret, and the secret cannot be read again after the dialog closes
  • The key is rotated with an overlap, expired and revoked, each shown in the list
  • A caller below the key's role sees the refusal named
  • A caller who holds apikeys.manage in one site sees that site's keys only
  • The secret is in no log, no draft and no browser storage, and a kept trace of the end-to-end run holds no screenshot of it
  • Component tests cover the create form, the secret and the refusals; the API tests check the records against the OpenAPI document; an end-to-end case makes a key and reads content with it

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

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.