{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T20:21:57.226Z",
  "record_id": "VXI-EXT-PROCUREMENT-OKTA-SESSION-TOKEN-01-v1",
  "record_kind": "external_reference",
  "title": "Okta: Session removal and OAuth-token revocation are separate",
  "system": "Okta",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does removing an Okta session prove that related API tokens were revoked?",
  "near_questions": [
    "Does identity-provider logout revoke API access?",
    "Are Okta sessions and OAuth tokens the same credential?",
    "Which option also revokes tokens when removing sessions?",
    "Does HTTP success prove a token was previously valid?",
    "Can revoking an access token leave its refresh token usable?",
    "What happens when the refresh token is revoked?",
    "Which offboarding operation should procurement record?",
    "How should an agent verify the intended revocation outcome?",
    "Can one session closure prove all sessions ended?",
    "What evidence covers application-specific sessions?",
    "When should complete logout remain unproven?",
    "Can I save an Okta revocation-scope review?"
  ],
  "supported_claims": [
    {
      "claim": "The guide separates session cookies from access and refresh tokens. Removing all user sessions can optionally include token revocation through a specific parameter. A successful revocation response also covers already-invalid tokens. Record the operation and its options, then verify the relevant access outcome.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "The guide separates session cookies from access and refresh tokens. Removing all user sessions can optionally include token revocation through a specific parameter. A successful revocation response also covers already-invalid tokens. Record the operation and its options, then verify the relevant access outcome.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-S3-PRESIGN-LIFETIME-01-v1",
    "VXI-EXT-PROCUREMENT-AZURE-SAS-REVOCATION-01-v1",
    "VXI-EXT-PROCUREMENT-CLOUDFLARE-SAAS-SESSION-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Okta token revocation and sessions",
    "source_url": "https://developer.okta.com/docs/guides/revoke-tokens/-/main/",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-OKTA-SESSION-TOKEN-01-v1",
    "candidate_record_sha256": "b1601c84740964c59e01b9c23b8adbcbe997b200206c3ec6c5e0e602d59bfaa6",
    "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": "The guide separates session cookies from access and refresh tokens. Removing all user sessions can optionally include token revocation through a specific parameter. A successful revocation response also covers already-invalid tokens. Record the operation and its options, then verify the relevant access outcome.",
    "required_buyer_context": "Session/token type, revocation operation, options and intended application access.",
    "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-14",
    "claim_to_check": "Successful session removal proves all related API access ended.",
    "documented_statement": {
      "status": "documented",
      "statement": "The guide separates session cookies from access and refresh tokens. Removing all user sessions can optionally include token revocation through a specific parameter. A successful revocation response also covers already-invalid tokens. Record the operation and its options, then verify the relevant access outcome.",
      "source_ids": [
        "okta-revoke"
      ]
    },
    "buyer_evidence_required": [
      "Exact session/token revocation operation and options.",
      "Relevant token family and application session inventory.",
      "Authorised verification of the intended access outcome."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not equate a successful session API response with complete token invalidation."
    },
    "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": "okta-revoke",
        "url": "https://developer.okta.com/docs/guides/revoke-tokens/-/main/",
        "final_url": "https://developer.okta.com/docs/guides/revoke-tokens/-/main/",
        "title": "Okta token revocation and sessions",
        "checked_on": "2026-10-14",
        "sha256": "fefcd9d37254b27dcb96a4c96b0eaf7d26427c5a83f15c813476201de60e3005",
        "bytes": 48076
      }
    ],
    "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": "Save what the offboarding action actually covered and which access outcomes still need proof.",
      "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": "Session/token inventory, operation options and application behaviour."
    }
  },
  "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#okta-session-token-revocation",
  "machine_readable_record": "/varexis-index/records/okta-session-token-revocation.json"
}