{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T07:59:18.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-SSO-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub tokens: SSO authorization has its own lifecycle",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does possessing a GitHub personal token prove it can access an SSO-linked organization?",
  "near_questions": [
    "Does a classic token need separate SSO authorization?",
    "When is a fine-grained token authorized?",
    "Can linked identity matter without enforced SSO?",
    "What happens after token scope changes?",
    "Does token regeneration preserve authorization?",
    "Can organization removal affect access?",
    "Who may revoke credential authorization?",
    "Does token validity prove SSO eligibility?",
    "Which organization is the token authorized for?",
    "What evidence can be shared without exposing the token?",
    "When should an agent request reauthorization instead of broader scopes?",
    "Can I retain an SSO-access review?"
  ],
  "supported_claims": [
    {
      "claim": "Classic personal tokens need SSO authorization for the organization; fine-grained tokens are authorized during creation. A linked SSO identity can require authorized credentials even without enforced SSO. Scope edits, regeneration, expiry or revocation can change that authorization.",
      "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": "Classic personal tokens need SSO authorization for the organization; fine-grained tokens are authorized during creation. A linked SSO identity can require authorized credentials even without enforced SSO. Scope edits, regeneration, expiry or revocation can change that authorization.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub personal-token SSO authorization",
    "source_url": "https://docs.github.com/en/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-SSO-01-v1",
    "candidate_record_sha256": "51cad18444a018a1ec5f7683362cb5d65fcd37300c1b7605e38b68afd58de686",
    "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": "Classic personal tokens need SSO authorization for the organization; fine-grained tokens are authorized during creation. A linked SSO identity can require authorized credentials even without enforced SSO. Scope edits, regeneration, expiry or revocation can change that authorization.",
    "required_buyer_context": "Token type, SSO linkage, authorization and lifecycle. Effective buyer configuration and dated operational evidence are required.",
    "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-16",
    "claim_to_check": "A valid personal token automatically retains organization SSO access.",
    "documented_statement": {
      "status": "documented",
      "statement": "Classic personal tokens need SSO authorization for the organization; fine-grained tokens are authorized during creation. A linked SSO identity can require authorized credentials even without enforced SSO. Scope edits, regeneration, expiry or revocation can change that authorization.",
      "source_ids": [
        "github-sso"
      ]
    },
    "buyer_evidence_required": [
      "Token type and linked organization identity.",
      "SSO authorization state.",
      "Token changes, expiry and organization membership."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require current organization authorization without asking the user to disclose the token."
    },
    "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": "github-sso",
        "url": "https://docs.github.com/en/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on",
        "final_url": "https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on",
        "title": "GitHub personal-token SSO authorization",
        "checked_on": "2026-10-16",
        "sha256": "d8b4323d9f98171f9ab66a9dab79b0ab03a243c3a5fbbdce3f43e731b90a6eaa",
        "bytes": 163192
      }
    ],
    "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 the authorization-state checks needed to diagnose access without widening credentials.",
      "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": "Token type, SSO linkage, authorization and lifecycle"
    }
  },
  "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#github-pat-sso-authorization-lifecycle",
  "machine_readable_record": "/varexis-index/records/github-pat-sso-authorization-lifecycle.json"
}