Achieving Single-Sign-On Agentic access to SAP with AWS for SAP MCP Server

Picture a finance analyst asking an AI assistant, “which of my customer invoices are overdue?” and getting an answer straight from SAP. Enterprises want exactly this, but connecting an AI agent to a system of record raises a hard question: when the agent reaches SAP, who is making the request? Many early integrations route every request through one shared SAP service user. This maps every user’s activity to a single technical user, so SAP can no longer authorize or audit the real operator, and it forces storage of static SAP credentials that security and compliance teams rarely approve. As a result, promising AI pilots stall before they reach production. Full identity propagation solves this by carrying each user’s identity through every authentication leg to SAP. When the request arrives as the named user, SAP applies that user’s own authorizations, logs the action against that user in the Security Audit Log, and stores no shared standing credential. On-Behalf-Of (OBO) access, defined in RFC 8693 token exchange, makes this possible by exchanging a user’s existing token for a downstream token scoped to SAP. Enterprise Identity providers (IdPs) such as Microsoft Entra ID and Okta su...