{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T12:05:03.000Z",
  "record_id": "VXI-EXT-PROCUREMENT-OAUTH-EXACT-REDIRECT-URI-COMPARISON-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "OAuth exact redirect URI comparison",
  "system": "IETF OAuth",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an OAuth server replace exact redirect URI matching with a trusted parent-domain check?",
  "near_questions": [
    "Is a wildcard OAuth callback equivalent to exact redirect matching?",
    "What localhost port exception applies to native OAuth clients?",
    "Can a trusted parent domain authorise a different OAuth redirect path?",
    "Which callback details must be checked before accepting an OAuth redirect?"
  ],
  "supported_claims": [
    {
      "claim": "RFC 9700 requires exact string matching against pre-registered redirect URIs, apart from the localhost port exception for native applications. A parent-domain match or a general wildcard is not that comparison. The guidance also prohibits open redirectors in clients and authorization servers.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Validated deployment security or permission to broaden registered callback destinations",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "RFC 9700 requires exact string matching against pre-registered redirect URIs, apart from the localhost port exception for native applications. A parent-domain match or a general wildcard is not that comparison. The guidance also prohibits open redirectors in clients and authorization servers.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "RFC 9700: Best Current Practice for OAuth 2.0 Security",
    "source_url": "https://www.rfc-editor.org/rfc/rfc9700.txt",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-OAUTH-EXACT-REDIRECT-URI-COMPARISON-BOUNDARY-01-v1",
    "candidate_record_sha256": "71f2f365f8a124ff2c282dea92711a1f7563c47afc0bc60a53db4f081f3398aa",
    "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 9700 requires exact string matching against pre-registered redirect URIs, apart from the localhost port exception for native applications. A parent-domain match or a general wildcard is not that comparison. The guidance also prohibits open redirectors in clients and authorization servers.",
    "required_buyer_context": "Registered redirect URI and actual authorization request URI; Client application type and any localhost port exception; Callback redirect behaviour and server comparison configuration. 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-24",
    "claim_to_check": "Can an OAuth server replace exact redirect URI matching with a trusted parent-domain check?",
    "documented_statement": {
      "status": "documented",
      "statement": "RFC 9700 requires exact string matching against pre-registered redirect URIs, apart from the localhost port exception for native applications. A parent-domain match or a general wildcard is not that comparison. The guidance also prohibits open redirectors in clients and authorization servers.",
      "source_ids": [
        "rfc9700"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review the exact registered callback and allowed exception rather than assuming every destination under a trusted domain is acceptable.",
      "source_ids": [
        "rfc9700"
      ]
    },
    "buyer_evidence_required": [
      "Registered redirect URI and actual authorization request URI",
      "Client application type and any localhost port exception",
      "Callback redirect behaviour and server comparison configuration"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not rely on a trusted parent domain as evidence that the exact callback destination was authorised."
    },
    "unknowns": "The buyer server's matching behaviour, callback integrity and current registration were not tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer server's matching behaviour, callback integrity and current registration were not tested."
    },
    "evidence_sources": [
      {
        "source_id": "rfc9700",
        "url": "https://www.rfc-editor.org/rfc/rfc9700.txt",
        "final_url": "https://www.rfc-editor.org/rfc/rfc9700.txt",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:34:50.484Z",
        "sha256": "9919d061d40a97886ca866b51c69389b6c81c65cd4b979056c14fdbebfcf622a",
        "bytes": 124673,
        "title": "RFC 9700: Best Current Practice for OAuth 2.0 Security",
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "version_context": "Published RFC9700; exact captured RFC text",
        "reviewed_sections": [
          "2.1.1 Authorization Code Grant",
          "2.5 Client Authentication",
          "4.1.3 Countermeasures for redirect URI validation attacks"
        ],
        "claim_review_completed": true
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid redirecting authorization results to an unapproved callback destination.",
      "free": "Complete review, sources, practical questions 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": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid redirecting authorization results to an unapproved callback destination.",
    "refusal_conditions": [
      "Do not rely on a trusted parent domain as evidence that the exact callback destination was authorised."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Avoid redirecting authorization results to an unapproved callback destination.",
    "comparison_role": "supplementary_discovery"
  },
  "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-exact-redirect-uri-comparison-boundary",
  "machine_readable_record": "/varexis-index/records/oauth-exact-redirect-uri-comparison-boundary.json"
}
