{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T17:54:06.066Z",
  "record_id": "VXI-EXT-PROCUREMENT-OAUTH-EXCHANGE-REVOCATION-01-v1",
  "record_kind": "external_reference",
  "title": "OAuth token exchange: Independent token lifecycles",
  "system": "OAuth 2.0 Token Exchange",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does revoking an input token automatically revoke every token obtained through OAuth token exchange?",
  "near_questions": [
    "Does OAuth token exchange propagate revocation?",
    "Does renewing the subject token renew the exchanged token?",
    "Which issuer controls the downstream token lifetime?",
    "Can an exchanged credential outlive the input grant?",
    "What revocation mechanism covers delegated agent tokens?",
    "Are input and output audiences recorded?",
    "Is cascading revocation deployment-specific?",
    "Which downstream tokens need separate offboarding?",
    "What token types were exchanged?",
    "Does RFC 8693 guarantee a shared token lifecycle?",
    "What evidence shows the receiving service refused access?",
    "Can a token-exchange diagram prove all delegated access ended?"
  ],
  "supported_claims": [
    {
      "claim": "RFC 8693 does not define a tightly coupled lifecycle between input and exchanged tokens. Input renewal need not change the output token, and revocation propagation depends on the implementation, token type and deployment. Token exchange alone is not evidence of cascading revocation.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic cascade revocation, matched lifetimes or verified revocation behaviour of any particular OAuth deployment",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "RFC 8693 does not define a tightly coupled lifecycle between input and exchanged tokens. Input renewal need not change the output token, and revocation propagation depends on the implementation, token type and deployment. Token exchange alone is not evidence of cascading revocation.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "RFC 8693: OAuth 2.0 Token Exchange",
    "source_url": "https://www.rfc-editor.org/rfc/rfc8693.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-OAUTH-EXCHANGE-REVOCATION-01-v1",
    "candidate_record_sha256": "3dc0369a2a90732da017e3a357eb62364080e1dcaec7178cfb85817042c4ef5a",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "RFC 8693 does not define a tightly coupled lifecycle between input and exchanged tokens. Input renewal need not change the output token, and revocation propagation depends on the implementation, token type and deployment. Token exchange alone is not evidence of cascading revocation.",
    "required_buyer_context": "Issuers, token types, audiences and non-secret identifiers for the exchange chain. Input and output expiries and the deployment-specific revocation propagation contract. Revocation results and access evidence at each relying service. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does revoking an input token automatically revoke every token obtained through OAuth token exchange?",
    "documented_statement": {
      "status": "documented",
      "statement": "RFC 8693 does not define a tightly coupled lifecycle between input and exchanged tokens. Input renewal need not change the output token, and revocation propagation depends on the implementation, token type and deployment. Token exchange alone is not evidence of cascading revocation.",
      "source_ids": [
        "oauth-exchange"
      ]
    },
    "buyer_evidence_required": [
      "Issuers, token types, audiences and non-secret identifiers for the exchange chain.",
      "Input and output expiries and the deployment-specific revocation propagation contract.",
      "Revocation results and access evidence at each relying service."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline chain-wide revocation claims without a documented propagation mechanism and matching downstream evidence."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "oauth-exchange",
        "url": "https://www.rfc-editor.org/rfc/rfc8693.html",
        "final_url": "https://www.rfc-editor.org/rfc/rfc8693.html",
        "title": "RFC 8693: OAuth 2.0 Token Exchange",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T17:50:55.839Z",
        "version_context": "RFC 8693, January 2020, section 2.1",
        "sha256": "cad0eccfa08d8c57eb096c2750e6cc783f8697b8771558943971fa58caff0fca",
        "bytes": 145221,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Section 2.1 Request"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Delegated agent chains can cross issuers and resources; offboarding requires knowing which issued credentials have their own lifetime or revocation path.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Issuers, token types, audiences and non-secret identifiers for the exchange chain. Input and output expiries and the deployment-specific revocation propagation contract. Revocation results and access evidence at each relying service."
    },
    "buyer_relevance": "Delegated agent chains can cross issuers and resources; offboarding requires knowing which issued credentials have their own lifetime or revocation path.",
    "refusal_conditions": [
      "Decline chain-wide revocation claims without a documented propagation mechanism and matching downstream evidence."
    ]
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#oauth-token-exchange-no-automatic-revocation-link",
  "machine_readable_record": "/varexis-index/records/oauth-token-exchange-no-automatic-revocation-link.json"
}
