{
  "format": "agent-article-v0",
  "article_id": "EA-044",
  "canonical_url": "/tools/ea-044-delegated-authorization",
  "page_type": "reference",
  "claim_ids": [],
  "evidence_ids": [
    "EA-044-R11-RESEARCH",
    "EA-044-R11-WEB-READBACK"
  ],
  "unknown_ids": [
    "EA-044-UNKNOWN-01",
    "EA-044-UNKNOWN-CURRENTNESS"
  ],
  "operational_object_ids": [],
  "provider": [],
  "models": [],
  "plans": [],
  "surfaces": [],
  "regions": [],
  "current_status": "UNKNOWN",
  "observation_status": "SPEC_ONLY",
  "freshness": "UNKNOWN",
  "last_verified": null,
  "supersedes": [],
  "superseded_by": [],
  "provenance": [
    "RESCUE-001-EA0044",
    "WEBBODY-EA0044-R8-7DDB80AD"
  ],
  "article_sources": [
    {
      "id": "EA-044-R11-RESEARCH",
      "evidence_class": "RESEARCH",
      "title": "EA-044 監査済みresearch / canonical revision binding",
      "supports": [
        "Delegated Authorization"
      ],
      "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。",
      "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET",
      "source_or_experiment_ids": [
        "RESCUE-001-EA0044"
      ],
      "supporting_locators": [
        "RESCUE-001-EA0044",
        "EA-044-R5-LEGACY-MIGRATION-20261008-R1",
        "content/staging/EA-044.md"
      ],
      "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。",
      "provenance_status": "AUDIT_PASS_CANONICAL_BINDING"
    },
    {
      "id": "EA-044-R11-WEB-READBACK",
      "evidence_class": "IMPL",
      "title": "EA-044 Web body identity / canonical readback",
      "supports": [
        "canonical staging bodyのSHA-256一致とR9 canonical ledger readbackをProduction projectionの入力として検証する。"
      ],
      "limit": "body identity/readbackは本文claim自体の真偽や外部ソースの最新性を追加保証しない。",
      "checked_at": null,
      "origin_class": "IMPLEMENTATION_READBACK",
      "source_or_experiment_ids": [
        "WEBBODY-EA0044-R8-7DDB80AD"
      ],
      "supporting_locators": [
        "WEBBODY-EA0044-R8-7DDB80AD",
        "content/staging/EA-044.md",
        "EA-044-R5-LEGACY-MIGRATION-20261008-R1"
      ],
      "scope": "R9/R10 canonical readback後のProduction生成時body identity。",
      "provenance_status": "CANONICAL_READBACK_BODY_HASH_MATCH"
    }
  ],
  "research_sections": [
    {
      "heading": "公開claim",
      "text": "**ESTABLISHED** — userのon-behalf-of実行は、application permission、token copying、untracked impersonationと同義ではない。delegationはresource／audience、permission、actor／client、user subject、lifetime、downstream policyで制約されるauthorization chainとして扱う。\n\n**ESTABLISHED** — RFC 8693はOAuth 2.0 Token ExchangeとしてSTS型のtoken exchangeを定義し、delegation／impersonation semanticsおよびtarget resource／audience parameterを提供する。ただしorganization trust modelやbusiness permission modelまでは定義しない。\n\n**ESTABLISHED** — RFC 9396は`authorization_details`によるfine-grained authorization requestを定義する。authorization intentを表現できることは、その要求がruntimeで自動的にenforceされることを意味しない。\n\n**ESTABLISHED** — RFC 9700はOAuth 2.0のcurrent security best practiceをまとめ、弱いpatternの扱いを更新する。\n\n**ESTABLISHED** — Amazon Bedrock AgentCoreのon-behalf-of token exchangeは、inbound user tokenをdownstream scoped tokenへ交換し、userとworkload／agent identity signalを伝播できる実装面を持つ。最終的なauthorization decisionはauthorization server側に残る。"
    },
    {
      "heading": "Delegation contract",
      "text": "user-delegated authorization、machine／application authorization、impersonation、token exchangeを別概念として保持する。\n\n各downstream hopでauthorizationを再評価する。upstream consentをblanket permissionとして扱わない。actor-chain evidenceとrevocation propagationはprotocol minimumを超える運用要件になり得る。"
    },
    {
      "heading": "UNKNOWN",
      "text": "- provider-specific OBO／token-exchange／RAR support\n- actor-chain retention\n- revocation propagation\n- tenant policy\n- proof-of-possession adoption\n- durable actor logging\n- implementation acceptance"
    },
    {
      "heading": "STOP_CONDITION",
      "text": "RFC 8693のtoken-exchange mechanics、RFC 9396のrich authorization、RFC 9700のsecurity BCP、およびcurrent agent implementationを、least privilege、durable audit、immediate revocationの自動保証として扱わない。provider supportとrevocation behaviorはPRODUCT_VOLATILE／UNKNOWNとして保持する。"
    }
  ],
  "human_url": "/tools/ea-044-delegated-authorization",
  "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-044-delegated-authorization",
  "json_url": "/agent/article.json?path=%2Ftools%2Fea-044-delegated-authorization"
}