docs: record measured AWS vs Azure session revocation behaviour - #74
Merged
Merged
Conversation
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.
Records what was measured against a live tenant on 2026-08-18.
REVOCATION_NOT_APPLICABLEsts:GetCallerIdentitysucceeded after the revokeREVOCATION_IN_PROGRESSREVOCATION_IN_PROGRESSCause: AWS exposes no session-scoped revocation primitive. STS tokens cannot be invalidated, and the alternatives (
aws:TokenIssueTimedeny, removing permissions) are role-scoped and would hit every concurrent session on that role. Azure/Entra elevations are role assignments, which are individually removable. This is an AWS constraint, not a product gap.Operational consequence:
grant revokecannot contain leaked AWS credentials.Also confirmed:
REVOCATION_NOT_APPLICABLEis absent from the live public OpenAPI spec (which still enumerates onlySUCCESSFULLY_REVOKEDandREVOCATION_IN_PROGRESS) and returns zero web hits — which is whyClassifyRevocationStatusmust keep failing closed.Docs only; no code change. The provider-neutral rule for user-facing text is explicitly preserved.