Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Trust policy principals are matched by ARN and are not bound to a unique id

Abierto
  • ¿Algo no está bien?
#443 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
aws, rust
Área
authentication, security

Línea de trabajo

Start with principal_entry_matches in crates/server/src/management/assume_role.rs, then trace where trust policies are saved and how role and user IDs are assigned. Compare the behavior with the IAM trust policy rules described in the issue. Done means a trust policy bound to a principal stops matching a recreated role or user with the same ARN, while the documented account and root principal matches still work.

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

Descripción

What ExtendDB does

principal_entry_matches in crates/server/src/management/assume_role.rs compares a trust policy Principal entry against the caller by exact ARN string, with extra matches for a bare account id and the arn:aws:iam::<account>:root form. ExtendDB stores no principal unique id. A role or user that is deleted and recreated with the same name keeps the same ARN, so it matches a trust policy written for the original principal.

What IAM does

The IAM User Guide (the Principal element of a role trust policy) states that IAM converts a role or user ARN in a trust policy to the principal's unique id when the policy is saved, so a principal that is deleted and recreated with the same name no longer matches. Measured across a delete and recreate: GetRole returns a new RoleId and GetUser a new UserId for the recreated principal.

Effect

A trust relationship meant for one incarnation of a role or user is inherited by a later principal that carries the same name. Deleting and recreating a principal does not drop the trust another role extended to the earlier one.

Suggested fix

Bind a trust policy's named principal to the principal's unique id at write time and match on that id, so a recreated same-named principal does not satisfy a trust policy written for the earlier one.

Lenguaje dominante
Rust
Estrellas
517
Forks
60
Merge medio
2 d 23 h
PR fusionados (30 d)
25

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 ExtendDB/extenddb

Todos los issues de ExtendDB/extenddb

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.