Repository navigation
Authenticate cluster identities and authorize operations from applied policy - #691
Merged
Merged
Conversation
aaltshuler
force-pushed
the
codex/identity-policy
branch
from
September 16, 2026 14:23
0b7cacf to
03914c3
Compare
aaltshuler
force-pushed
the
codex/identity-policy
branch
from
September 16, 2026 14:47
03914c3 to
3b9edfa
Compare
aaltshuler
marked this pull request as ready for review
September 16, 2026 14:47
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.
Signed credentials currently duplicate graph/action permissions already held in policy. Version 2 credentials authenticate a principal for one cluster; the applied Cedar policy owns graph, schema and configuration permissions. Minimal discovery exposes every effective graph ID/name without granting access to data, schema or query definitions.
The shared cluster API authorizes the complete configuration plan against current applied policy, repeats checks under the existing lock, and refuses candidate self-grants, changed bases and pending recovery. Initial policy installation uses an exact first-initialization boundary. The new recovery probe inspects bounded storage metadata without opening or repairing the graph.
The CLI preserves complete typed HTTP errors for both
--jsonand--format json. Denial regressions verify structured errors and unchanged graph snapshots/branch inventory.Compatibility:
config_managerule before identity-authorized configuration execution. Public exhaustive policy matches need the newConfigManage/Clustervariants.The accepted design is
docs/rfcs/2026-09-09-identity-credentials-and-applied-policy.md. This PR builds on the merged bounded-transport change in #685.Validation: the JSON-format failure was reproduced before the fix; four focused remote CLI tests and six policy-enforcement cases pass. Formatting, documentation and link checks pass; recovery code and tests use current seam APIs. On the final head, canonical local workspace/failpoint tests pass (3,182 passed, 25 ignored), as do 149 GQT library and 14 runner-dispatch tests. Full workspace, GQ, DST, server AWS, both RustFS suites and format/upgrade CI pass. Locally unconfigured cloud/predecessor fixtures are qualified by their configured CI jobs.