Decide: report or prune unmanaged p and g2 rows

Aperta
#613 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
authorization

Direzione di ricerca

This is a design decision, not a code fix. Start with ADR 0034 (docs/decisions/0034-permission-dependencies-in-authorization-schema.rst), ADR 0025 on source tracking, and the review thread on PR #601 to see what has already been argued. Done means a recorded decision on reporting and pruning of unmanaged p and g2 rows, with the ADRs and operational docs updated and tests or command checks for the chosen behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

discovery documentation

Background

ADR 0034 (Permission Dependencies in Authorization Schema) defines how permission dependencies are declared in the authorization schema and rendered as Casbin g2 rows. ADR 0025 establishes source tracking for schema-managed policy rows, while leaving unmanaged rows in place.

Current state: A stored p or g2 row that no schema declares remains enforceable but unattributed. The system does not yet define how operators discover, audit, report, or remove those rows.

Concern: Unmanaged rows may be intentional legacy or database-only configuration, but they can also persist after schema changes without a clear lifecycle or visibility mechanism.

Scope of work

Decide how openedx-authz should handle policy rows that remain in storage without a matching schema declaration:

  1. Reporting: Define whether loading, validation, inspection commands, or administrative tooling should report unmanaged p and g2 rows, and what information the report must include.
  2. Pruning: Decide whether rows can be removed automatically, only through an explicit command or flag, or not at all.
  3. Safety: Define safeguards for distinguishing intentional database-only configuration from stale rows and for preventing accidental privilege removal.
  4. Lifecycle: Document how the chosen behavior applies during schema upgrades, permission removal, and migration from legacy policy files.

Acceptance criteria

  • A decision is made on reporting unmanaged p and g2 rows.
  • A decision is made on whether and how unmanaged rows may be pruned.
  • The decision defines safeguards against accidental privilege removal.
  • The relevant ADRs and operational documentation are updated.
  • Tests or command-level checks cover the chosen behavior.

References

Lingua principale
Python
Stelle
0
Fork
10
Merge medio
5g 12h
PR unite (30g)
23

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openedx/openedx-authz

Tutte le issue di openedx/openedx-authz

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.