fix(auth): harden assertion and provider evidence - #4782
Closed
cea-block wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Cea Stapleton Cordasco <261786559+cea-block@users.noreply.github.com>
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
1 participant
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.
Why
Protected authorization needs one fail-closed trust boundary for ambiguous identity inputs, bounded assertion time, provider key degradation, and provider-neutral verified evidence.
What
VerifiedProviderEvidencecontract bound to the exact domain, transport, installed profile, normalized principal, capability set, and hard freshness window.Risk Assessment
The new behavior is disabled unless the protected authorization profile is installed. Mismatched, stale, future, or ambiguous evidence fails closed. No migrations are introduced.
References
Stacked on #4772.
Generated with Codex