{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-SALESFORCE-CLIENT-CREDENTIALS-RUN-AS-AUTHORITY-01-v1",
  "record_kind": "external_reference",
  "title": "Salesforce client credentials run-as identity",
  "system": "Salesforce",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can the documented Salesforce connected-app client-credentials flow operate without a configured run-as user?",
  "near_questions": [
    "Does Salesforce client credentials need an execution user?",
    "Whose permissions govern a Salesforce integration token?",
    "Can a client secret replace the Salesforce run-as identity?",
    "What must be checked before enabling the connected-app flow?"
  ],
  "supported_claims": [
    {
      "claim": "Salesforce’s connected-app guide requires enabling client credentials and selecting an execution or run-as user. API actions use that user’s permissions, with the integration-user licence and permission configuration considered separately. A client identifier and secret do not replace the execution identity. This is the documented 2024 connected-app flow, not a claim about new-app provisioning defaults.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Unrestricted API access from client secret possession",
    "The buyer’s app type, policy and integration-user permissions are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Salesforce’s connected-app guide requires enabling client credentials and selecting an execution or run-as user. API actions use that user’s permissions, with the integration-user licence and permission configuration considered separately. A client identifier and secret do not replace the execution identity. This is the documented 2024 connected-app flow, not a claim about new-app provisioning defaults.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Invoke REST APIs with the Salesforce Integration User and OAuth Client Credentials | Salesforce Developers Blog",
    "source_url": "https://developer.salesforce.com/blogs/2024/02/invoke-rest-apis-with-the-salesforce-integration-user-and-oauth-client-credentials",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SALESFORCE-CLIENT-CREDENTIALS-RUN-AS-AUTHORITY-01-v1",
    "candidate_record_sha256": "e6684288deaea6b6cc85db68ee398f93d6ea4ba22fb2052e199c82657a886477",
    "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": "Salesforce’s connected-app guide requires enabling client credentials and selecting an execution or run-as user. API actions use that user’s permissions, with the integration-user licence and permission configuration considered separately. A client identifier and secret do not replace the execution identity. This is the documented 2024 connected-app flow, not a claim about new-app provisioning defaults.",
    "required_buyer_context": "Connected-app client-credentials policy and run-as user; Integration-user licence and assigned permissions; Required API operations and their access checks. 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 the documented Salesforce connected-app client-credentials flow operate without a configured run-as user?",
    "documented_statement": {
      "status": "documented",
      "statement": "Salesforce’s connected-app guide requires enabling client credentials and selecting an execution or run-as user. API actions use that user’s permissions, with the integration-user licence and permission configuration considered separately. A client identifier and secret do not replace the execution identity. This is the documented 2024 connected-app flow, not a claim about new-app provisioning defaults.",
      "source_ids": [
        "salesforce-client"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review the chosen integration user and least-privilege permissions alongside the OAuth configuration.",
      "source_ids": [
        "salesforce-client"
      ]
    },
    "buyer_evidence_required": [
      "Connected-app client-credentials policy and run-as user",
      "Integration-user licence and assigned permissions",
      "Required API operations and their access checks"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not approve authority from client credentials without the configured execution user."
    },
    "unknowns": "The buyer’s app type, policy and integration-user permissions are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer’s app type, policy and integration-user permissions are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "salesforce-client",
        "url": "https://developer.salesforce.com/blogs/2024/02/invoke-rest-apis-with-the-salesforce-integration-user-and-oauth-client-credentials",
        "final_url": "https://developer.salesforce.com/blogs/2024/02/invoke-rest-apis-with-the-salesforce-integration-user-and-oauth-client-credentials",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:47:26.658Z",
        "sha256": "2b4b78b2efcb8486e7fbd2860cac116397f03a43264a22e5d9296ce869bed894",
        "bytes": 60850,
        "title": "Invoke REST APIs with the Salesforce Integration User and OAuth Client Credentials | Salesforce Developers Blog",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Connected app client-credentials enablement and run-as user"
        ],
        "version_context": "Salesforce developer guide published February 2024; connected-app client-credentials flow. Does not establish current new-app creation defaults."
      }
    ],
    "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": "Bind unattended API access to an explicit and reviewed integration 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": "Bind unattended API access to an explicit and reviewed integration identity.",
    "refusal_conditions": [
      "Do not approve authority from client credentials without the configured execution user."
    ]
  },
  "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": "Bind unattended API access to an explicit and reviewed integration 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#salesforce-client-credentials-run-as-authority",
  "machine_readable_record": "/varexis-index/records/salesforce-client-credentials-run-as-authority.json"
}
