OAuth 2.0 SAML Bearer Assertion Grant
The concept name was not provided and cannot be determined from the available source snippets, which cover topics such as inbound communication via principal propagation, OAuth 2.0 SAML Bearer Assertion Grant, and integration between SAP BTP ABAP Environment and SAP S/4HANA Cloud. Please supply the concept name so a grounded, accurate definition can be written.
Tutorials that teach this
- Tutorial Learn the basic concepts required for the integration of SAP BTP, ABAP environment and SAP S/4HANA Cloud, public edition
- Tutorial Integrate SAP BTP ABAP Environment and SAP S/4HANA Cloud, public edition using the OAuth 2.0 SAML Bearer Assertion Flow
- Tutorial Access Protected SAP Analytics Cloud Resources with OAuth Two-Legged Flow
Docs explaining this concept
Prerequisites
- Concept Basic Authentication for SAP BTP ABAP Environment and SAP S/4HANA Cloud Integration
- Concept SAML Identity Provider Trust Configuration The provided sources do not contain enough grounded information to define a concept labeled "undefined." Based on the available sources, they collectively describe **SAML trust configuration** on SAP BTP — a mechanism that allows developers to establish federated trust between SAP BTP subaccounts and identity providers (such as [SAP Cloud Identity Services](https://help.sap.com/docs/btp/sap-business-technology-platform/7c6aa87459764b179aeccadccd4f91f3?locale=en-US&state=PRODUCTION&version=Cloud) or SAP SuccessFactors) using the SAML 2.0 protocol. Developers use it to enable single sign-on, map identity provider groups to platform roles, and configure OAuth 2.0 SAML Bearer Assertion grants for secure service-to-service communication. It can also be [restored after replacement](https://help.sap.com/docs/btp/sap-business-technology-platform/21d86cf36ce94da7b2f2db8271e0b539?locale=en-US&state=PRODUCTION&version=Cloud) to recover a previous trust setup in a subaccount.
- Concept OAuth 2.0 Authentication The concept name provided is undefined and the supplied sources do not share a common subject — they cover a Communication Arrangement outbound user entity, Web Access Control in the Cloud Foundry environment, and an augmented reality tutorial — making it impossible to ground a coherent definition in the given material. Please provide a valid concept name and relevant supporting sources so an accurate definition can be written.
- Concept Basic Authentication The concept name was not provided, but based on the sources, this appears to relate to **inbound communication authentication** in SAP BTP, ABAP environment. A Communication User is a technical user configured to enable inbound communication, allowing external clients to authenticate and connect to SAP BTP services. Developers use it alongside authentication methods such as [Basic Authentication](https://help.sap.com/docs/btp/sap-business-technology-platform/4e1761cecbdd47f6b93e1dfd9d254281?locale=en-US&state=PRODUCTION&version=Cloud) or OAuth to secure [inbound communication channels](https://help.sap.com/docs/btp/sap-business-technology-platform/7e73616a62e0455dab6574ead2073383?locale=en-US&state=PRODUCTION&version=Cloud). When using Basic Authentication, the client supplies the credentials of the Communication User to gain access to the system.
- Concept Communication Systems Configuration The provided sources do not contain sufficient information to define the concept **"undefined"** — no concept name or relevant explanatory content was supplied. A meaningful definition cannot be grounded solely in the available source snippets, which cover unrelated topics such as certificate renewal, communication systems, and SMTP integration. Please provide a valid concept name and supporting sources so an accurate, grounded definition can be written.
- Concept SAML 2.0 and OpenID Connect Protocols SAML 2.0 and OpenID Connect are industry-standard protocols used to enable [identity federation](https://help.sap.com/docs/btp/sap-business-technology-platform/2abdc1d4373648799a8b1275084b7975?locale=en-US&state=PRODUCTION&version=Cloud) on SAP Business Technology Platform — the process of sharing identity information between two parties. Developers use these protocols to establish trust between an identity provider and SAP BTP, allowing users to authenticate through a central identity provider rather than managing separate credentials for each service.
- Concept Communication Arrangement in SAP BTP ABAP Environment The concept name is not defined in the provided sources, and the available source snippets do not contain sufficient shared context to identify and describe a single, specific SAP developer concept. A meaningful, source-grounded definition cannot be produced.
- Concept Service Consumption Models (SRVC) A **Service Consumption Model** is an ABAP development object used to consume external services — such as OData, SOAP, or RFC-based services — from within the SAP BTP, ABAP Environment. Developers use it to generate the necessary proxy classes and artifacts that allow ABAP code to call remote services in a structured, type-safe way. It supports scenarios such as [consuming SOAP-based web services](https://help.sap.com/docs/btp/sap-business-technology-platform/76a5171118384beea71ca593b096eedc?locale=en-US&state=PRODUCTION&version=Cloud) or generating RFC proxy classes for remote function call integration.
- Concept Communication Arrangement for Cloud Connector A **Communication Arrangement** is a configuration object in the ABAP environment of SAP Business Technology Platform that defines how an external system connects to and communicates with your system. Developers use it to set up integration scenarios by specifying a [communication scenario, system, and user](https://help.sap.com/docs/btp/sap-business-technology-platform/04488354490349f989871c5d555a2926?locale=en-US&state=PRODUCTION&version=Cloud), enabling both inbound and outbound connections. The [communication management apps](https://help.sap.com/docs/btp/sap-business-technology-platform/2e84a10c430645a88bdbfaaa23ac9ff7?locale=en-US&state=PRODUCTION&version=Cloud) allow developers to integrate their system with other systems, such as SAP Analytics Cloud, SAP Datasphere, or on-premise systems via Cloud Connector, as well as services like outbound email via SMTP.
- Concept Communication System A **Communication System** is an external system or service registered in SAP BTP that a developer or administrator connects to for integration purposes. You can use the [Communication Systems](https://help.sap.com/docs/btp/sap-business-technology-platform/15663c157670410ca366623dff329396?locale=en-US&state=PRODUCTION&version=Cloud) app to create and manage these systems, which serve as the technical counterpart when setting up communication arrangements. Together with communication users and arrangements, communication systems are part of the broader [Communication Management](https://help.sap.com/docs/btp/sap-business-technology-platform/2e84a10c430645a88bdbfaaa23ac9ff7?locale=en-US&state=PRODUCTION&version=Cloud) toolset that allows you to integrate your system with external solutions.