feat(policy): authorize authenticated principals - #85
Open
P4ST4S wants to merge 2 commits into
Open
Conversation
|
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Étend le moteur de policy aux identités authentifiées et conserve une projection minimale du principal dans chaque événement d’audit concerné.
Context
Cette PR dépend de #83 pour Principal/Auth et de #81 pour les primitives d’opération MCP. Le commit de #81 est présent sur cette branche d’intégration ; il disparaîtra du diff lorsque la dépendance sera fusionnée.
Approach
Test plan
Stability impact
Ajoute des sélecteurs optionnels à policy.rules et le champ audit principal. Les règles existantes gardent leur sémantique. Le principal audité ne contient jamais roles, scopes ni claims bruts.
Notes for reviewer
Le champ principal devra être inclus dans le payload Integrity v2 lors de l’intégration finale des branches d’audit ; la signature legacy reste volontairement inchangée conformément à STABILITY.md.