Unverified50% confidenceFactExact time
For S/4HANA public cloud, since Cloud Connector cannot be used, principal propagation instead uses an OAuth 2.0 to SAML 2.0 bearer assertion flow, with SAP Cloud Identity Services issuing the SAML assertion directly to S/4HANA.
1
Sources
50%
Confidence
Long-term
Relevance
10/20/2026
First Seen
Sources
SAP Meets MCP: 5 Architecture Patterns for AI Agents Connecting to S/4HANA
youtubeGP Satapathy10/20/2026
Related Entities
Related Claims
UnverifiedIn principal propagation mode, the user logs in to the MCP client via SAP Cloud Identity Services; the JWT token reaches Integration Suite, Cloud Connector issues a short-lived X.509 certificate for that user, and S/4HANA maps it to the real SAP user via certificate rules.74% similarUnverifiedSignature V4 is AWS's standard authentication mechanism for signing HTTP requests, widely used in API calls to AWS services such as S3, DynamoDB, and Lambda.62% similarUnverifiedCommon configuration management tools include HashiCorp Consul, Spring Cloud Config, etcd, AWS AppConfig, and Azure App Configuration.62% similarUnverifiedCommon SSO implementation protocols include SAML 2.0, OAuth 2.0, and OpenID Connect (OIDC).60% similarUnverifiedIn the mode of proxying cloud APIs, the Ollama local server acts as an intermediary layer forwarding client requests to the remote service, so developers do not need to hard-code cloud service addresses or credentials in client code.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1075212API
curl https://kongchang.com/api/v1/knowledge/claims/1075212MCP
get_claim(id=1075212)