{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-9-tranche-59-v1", "route_id": "agentic_reviewed_resource_omission_policy", "record_id": "VXI-EXT-PROCUREMENT-RESOURCE-OMISSION-POLICY-01-v1", "question": "Does omitting OAuth resource mean a token is valid at every resource server?", "answer": "RFC 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-RESOURCE-OMISSION-POLICY-01-v1", "url": "/varexis-index/records/resource-omission-policy.json", "content_sha256": "c732b3a22be7c1d0960e8da72abdf991218b802b8f84ad47ebc3de8058321ef3", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T20:55:19.974986+00:00", "record_id": "VXI-EXT-PROCUREMENT-RESOURCE-OMISSION-POLICY-01-v1", "record_kind": "external_reference", "title": "OAuth omitted resource policy", "system": "IETF RFC 8707", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does omitting OAuth resource mean a token is valid at every resource server?", "near_questions": [ "Does omitting OAuth resource mean access to every API?", "Can an authorization server reject a request without resource?", "Is the default resource identical for all OAuth servers?", "What audience evidence is needed when resource was omitted?" ], "supported_claims": [ { "claim": "RFC 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Include all three documented possibilities; the current buyer_decision mentions default or rejection but omits processing with no specific resource. No option alone establishes arbitrary-server acceptance.", "Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.", "No expanded capabilities or licences for existing INDEX executables." ], "public_summary": "RFC 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "IETF RFC 8707", "source_url": "https://www.rfc-editor.org/rfc/rfc8707.txt", "checked_on": "2026-10-25", "candidate_record_id": "VXI-EXT-PROCUREMENT-RESOURCE-OMISSION-POLICY-01-v1", "candidate_record_sha256": "1bac22cbde2f85f2a605a4537f32f3125fa35ef09198a0dcbea750c671b0cb38", "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 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.", "required_buyer_context": "Authorization-server policy; Request with omitted resource; Issued token restrictions or error. 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-25", "claim_to_check": "Does omitting OAuth resource mean a token is valid at every resource server?", "documented_statement": { "status": "documented", "statement": "RFC 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.", "source_ids": [ "rfc8707" ] }, "review_inference": { "status": "review_inference", "statement": "Require the server default or rejection policy before reasoning about omitted audience. This is a documentation-review judgment, not an observed deployment outcome.", "source_ids": [ "rfc8707" ] }, "buyer_evidence_required": [ "Authorization-server policy", "Request with omitted resource", "Issued token restrictions or error" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse buyer-specific assurance from documentation alone. Include all three documented possibilities; the current buyer_decision mentions default or rejection but omits processing with no specific resource. No option alone establishes arbitrary-server acceptance." }, "unknowns": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.", "unknown_finding": { "status": "unknown", "statement": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected." }, "evidence_sources": [ { "source_id": "rfc8707", "url": "https://www.rfc-editor.org/rfc/rfc8707.txt", "final_url": "https://www.rfc-editor.org/rfc/rfc8707.txt", "status": 200, "captured_at_utc": "2026-10-25T20:04:28.365Z", "sha256": "3b89844a938b9219571931b664ed4a7b380555a4dda1df4e9445a2f72188e76b", "bytes": 25698, "title": "IETF RFC 8707", "hash_basis": "SHA-256 of unmodified HTTP response body bytes", "rights_review": "Original factual paraphrase of the cited IETF RFC; IETF Trust and contributor rights remain applicable. No RFC text, code component or modified standard is redistributed.", "checked_on": "2026-10-25", "capture_status": 200, "claim_review_completed": true, "reviewed_sections": [ "Section 2", "Section 2.1", "Section 2.2", "Section 3" ], "version_context": "Fixed IETF RFC 8707 publication; later applicable updates and actual implementation conformance require separate review." } ], "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": "Require the server default or rejection policy before reasoning about omitted audience.", "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": "Recheck Section 2.1 in IETF RFC 8707 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval." }, "buyer_relevance": "Require the server default or rejection policy before reasoning about omitted audience.", "refusal_conditions": [ "Refuse buyer-specific assurance from documentation alone. Include all three documented possibilities; the current buyer_decision mentions default or rejection but omits processing with no specific resource. No option alone establishes arbitrary-server acceptance." ] }, "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": "Require the server default or rejection policy before reasoning about omitted audience.", "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#resource-omission-policy", "machine_readable_record": "/varexis-index/records/resource-omission-policy.json" } } ], "access": { "mode": "exact_http_only", "payment_required": false, "purchase_url": null, "mcp_preview_available": false, "paid_saved_retrieval_available": false, "natural_language_search_qualified": false }, "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.", "content_sha256": "ad5172cd8009dcbb38f2fc9dffb2d22dbc676621be3d7a37c7a23e407d95af35" }