{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T12:05:03.000Z",
  "record_id": "VXI-EXT-PROCUREMENT-OAUTH-CONFIDENTIAL-CLIENT-PKCE-AUTHENTICATION-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "OAuth PKCE and confidential client authentication",
  "system": "IETF OAuth",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can OAuth PKCE replace client authentication for a confidential authorization-code client?",
  "near_questions": [
    "Does a confidential OAuth client still authenticate when it uses PKCE?",
    "Are client authentication and PKCE the same OAuth control?",
    "What separates authorization-code binding from confidential-client identity?",
    "Can a PKCE verifier stand in for confidential client credentials?"
  ],
  "supported_claims": [
    {
      "claim": "RFC 9700 recommends PKCE for confidential clients as protection against authorization-code misuse. RFC 6749 separately requires client authentication for confidential clients or clients issued credentials when using the token endpoint. PKCE binds a code exchange to a verifier; it does not remove that client-authentication requirement.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Complete OAuth security or tested authentication from advertised PKCE support",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "RFC 9700 recommends PKCE for confidential clients as protection against authorization-code misuse. RFC 6749 separately requires client authentication for confidential clients or clients issued credentials when using the token endpoint. PKCE binds a code exchange to a verifier; it does not remove that client-authentication requirement.",
  "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-CONFIDENTIAL-CLIENT-PKCE-AUTHENTICATION-BOUNDARY-01-v1",
    "candidate_record_sha256": "68b3cb33148259a5807c4eb787ded3bb4da14dbf7a612bf0090c5cd6e5967687",
    "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 recommends PKCE for confidential clients as protection against authorization-code misuse. RFC 6749 separately requires client authentication for confidential clients or clients issued credentials when using the token endpoint. PKCE binds a code exchange to a verifier; it does not remove that client-authentication requirement.",
    "required_buyer_context": "Client registration and confidential or public classification; Token endpoint authentication method and enforcement evidence; Transaction-specific PKCE challenge and verifier handling. 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 OAuth PKCE replace client authentication for a confidential authorization-code client?",
    "documented_statement": {
      "status": "documented",
      "statement": "RFC 9700 recommends PKCE for confidential clients as protection against authorization-code misuse. RFC 6749 separately requires client authentication for confidential clients or clients issued credentials when using the token endpoint. PKCE binds a code exchange to a verifier; it does not remove that client-authentication requirement.",
      "source_ids": [
        "rfc9700",
        "rfc6749"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review the client type, authentication method and PKCE exchange as separate controls rather than treating one successful verifier check as both.",
      "source_ids": [
        "rfc9700",
        "rfc6749"
      ]
    },
    "buyer_evidence_required": [
      "Client registration and confidential or public classification",
      "Token endpoint authentication method and enforcement evidence",
      "Transaction-specific PKCE challenge and verifier handling"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not accept a confidential-client authentication claim supported only by PKCE use."
    },
    "unknowns": "The deployed authentication checks, credential storage and correct verifier validation are not established by the specifications.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The deployed authentication checks, credential storage and correct verifier validation are not established by the specifications."
    },
    "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
      },
      {
        "source_id": "rfc6749",
        "url": "https://www.rfc-editor.org/rfc/rfc6749.txt",
        "final_url": "https://www.rfc-editor.org/rfc/rfc6749.txt",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:34:50.114Z",
        "sha256": "f204fc8661d6c92d2ec6e0b54808f961a9ad26e792f57f312d9528335519bd71",
        "bytes": 163498,
        "title": "RFC 6749: The OAuth 2.0 Authorization Framework",
        "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 RFC6749; exact captured RFC text",
        "reviewed_sections": [
          "3.2.1 Client Authentication",
          "4.4 Client Credentials Grant"
        ],
        "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": "Check a connector login flow without confusing code interception protection with client identity.",
      "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": "Check a connector login flow without confusing code interception protection with client identity.",
    "refusal_conditions": [
      "Do not accept a confidential-client authentication claim supported only by PKCE use."
    ]
  },
  "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": "Check a connector login flow without confusing code interception protection with client identity.",
    "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-confidential-client-pkce-authentication-boundary",
  "machine_readable_record": "/varexis-index/records/oauth-confidential-client-pkce-authentication-boundary.json"
}
