Trace an agent to its parents, session, and user from the audit records

Abierto
#2,844 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start with the lineage design in docs/drafts/agent-identity/audit.md and the audit record and helper registration work in #2566 and #2555. Trace how gateway and decision records reference registrations and delegations, then identify the query or command entry point for following those references. Done means a trail from a helper gateway record reaches its parents, session, and user using audit records alone, with a test showing where and why an incomplete chain stops.

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

Descripción

agent-identity identity-broker

Depends on: #2566 (registration and delegation records), #2555 (helper registration)

Problem

A gateway record names only the acting agent's opaque SPIFFE ID. The agent's parents, session, and user are in the audit records, but nothing follows them. So an investigator cannot reconstruct who created or delegated to the agent that made a call.

Implements

Scope

  • A query that starts from a gateway record's act.sub or from a decision record. It follows registration references (who created the agent) and delegation references (who handed it the task) to the root, then to the session and the user. It reads the audit store only.
  • The records themselves are #2566's. Joins to ToolHive records by operation ID are #2848's.

Done when

  • The three implementation.md checks pass.
  • Starting from a helper's gateway record, the trail shows the helper, every parent up to the main agent, the session, and the user, from the audit records alone.
Lenguaje dominante
Go
Estrellas
309
Forks
29
Merge medio
15 h 56 min
PR fusionados (30 d)
225

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 stacklok/mecatl

Todos los issues de stacklok/mecatl

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.