OAuth2 SAML Bearer Assertion Authentication Setup
The concept name provided is "undefined," and the supplied sources do not define or describe a specific, identifiable SAP developer concept under that label. Without a valid concept name or supporting source content that describes a concrete technical topic, a grounded and accurate reference definition cannot be written. Please provide a valid concept name and relevant source snippets so a proper definition can be produced.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept Basic Authentication for Communication Arrangements The concept name was not provided (marked as "undefined"), and the single source snippet contains only a page title and fragment with no substantive descriptive content to ground a definition in. A accurate, source-grounded definition cannot be written without a valid concept name and supporting source material.
- Concept SAML/OIDC Federation The concept name was not provided (received "undefined"), and the available source snippet does not contain enough detail to ground a complete, accurate definition. A valid concept name and sufficient source material are required to produce a reliable reference definition.
- Concept Single Sign-On (SSO) and SAML Authentication The concept name is not defined in the provided sources, so a grounded definition cannot be written. Based on the available sources, which cover topics such as identity providers, trust and federation, single sign-on, and live data connections on SAP BTP, the specific concept intended here is unclear. Please provide a valid concept name so that an accurate, source-grounded definition can be produced.
- 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 for SAP BTP ABAP Environment and SAP S/4HANA Cloud Integration
- Concept SAP HANA Certificate and PSE (Certificate Collection) Management The concept name provided is "undefined," and the available sources do not contain sufficient information to define a specific, identifiable SAP developer concept. The sources reference topics such as [downloading certificates](https://help.sap.com/docs/btp/sap-business-technology-platform/3645813291be47839e72ab08d8a31ac9?locale=en-US&state=PRODUCTION&version=Cloud), X.509 authentication, SAP HANA Cloud data virtualization, and SAP Analytics Cloud connections, but without a concrete concept name, no accurate and grounded definition can be produced.
- 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 SAP S/4HANA Cloud Public Edition integration The concept is not defined in the provided sources. No source snippets contain sufficient information to write a grounded, accurate definition for an undefined concept.
- Concept Principal Propagation **Principal Propagation** is a mechanism on SAP Business Technology Platform that allows a user's identity (the "principal") to be forwarded from one application or service to another, preserving the original user context across system boundaries. Developers use it to enable [inbound communication via a business user](https://help.sap.com/docs/btp/sap-business-technology-platform/387b3deb12474762b593d4b1f2b392ad?locale=en-US&state=PRODUCTION&version=Cloud) so that downstream systems can apply the correct authorizations for that specific user rather than a generic technical user. It is also applied in [tightly coupled development scenarios](https://help.sap.com/docs/btp/sap-business-technology-platform/5ad748d634254363b2f0cb2b9679ac6f?locale=en-US&state=PRODUCTION&version=Cloud) and can be configured using protocols such as SAML Bearer Assertion or OAuth 2.0 SAML Bearer Assertion Grant to propagate user information between applications or services.
- 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 Trust configuration between SAP Cloud Identity Services and SAP BTP The provided sources do not contain enough information to define a specific, named SAP developer concept, as the concept supplied is "undefined." The sources relate to custom identity providers on SAP BTP, but without a concrete concept name or sufficient descriptive snippets, a grounded definition cannot be accurately composed.
- Concept OAuth2 Token Flow (Refresh and Access Tokens) The concept name was not provided (received "undefined"), so a grounded definition cannot be written. Please supply a valid concept name so that a definition can be authored from the available source snippets.
- Concept OAuth2 Client Credentials Grant Flow The provided sources do not contain sufficient information to define a specific, identifiable SAP developer concept — the concept name is listed as "undefined" and the source snippets cover a broad range of unrelated topics (OAuth2 Proxy, JWT security, API calls, service instances, and various tutorials) without converging on a single definable concept. A meaningful, source-grounded definition cannot be produced.
- Concept SAP BTP Communication Management (Scenario, System, Arrangement) The provided sources do not contain sufficient information to define the concept "undefined." The sources reference SAP BTP integration services such as [Certificates - Read Integration](https://help.sap.com/docs/btp/sap-business-technology-platform/10010aed8eac402184a84c222ebe75f2?locale=en-US&state=PRODUCTION&version=Cloud) and [Communication Arrangement - Read Integration](https://help.sap.com/docs/btp/sap-business-technology-platform/3ccd9a56e00441de93d8b519861dc56d?locale=en-US&state=PRODUCTION&version=Cloud), but none of them define or describe a concept named "undefined." No definition can be responsibly produced from the available source material.
- Concept SSL Certificate Generation and Management
- 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.
- Concept Trust Configuration between SAP S/4HANA and SAP Cloud Identity Services The concept name was not provided, and the supplied source snippets describe trust management between SAP Business Technology Platform (SAP BTP) and identity providers — but without a defined concept name or sufficient snippet content to extract a precise, grounded definition, a fully accurate definition cannot be produced. Based on the available context, this appears to relate to **identity provider trust configuration** on SAP BTP: a mechanism developers and administrators use to establish trust between an SAP BTP subaccount and an [SAP Cloud Identity Services tenant](https://help.sap.com/docs/btp/sap-business-technology-platform/6140107ac5da428a930cfefd73468628?locale=en-US&state=PRODUCTION&version=Cloud) or a [corporate identity provider](https://help.sap.com/docs/btp/sap-business-technology-platform/8980b91c14f9474a9d7c7d831bbad8e9?locale=en-US&state=PRODUCTION&version=Cloud) for authenticating platform users. This trust configuration allows organizations to delegate user authentication to an external identity provider rather than relying solely on SAP's default identity store.
- Concept Communication Arrangement Setup The concept name is not defined in the provided sources, so a grounded definition cannot be produced. The sources cover related SAP BTP topics such as [Communication Arrangements](https://help.sap.com/docs/btp/sap-business-technology-platform/1decd8b8747443ee8839ce4474a3643e?locale=en-US&state=PRODUCTION&version=Cloud) and [Manage Git Repository](https://help.sap.com/docs/btp/sap-business-technology-platform/0882b7f82736431d8b145913af17b532?locale=en-US&state=PRODUCTION&version=Cloud), but none of them define a concept identified as "undefined." Please provide a valid concept name so that an accurate, source-grounded definition can be written.
- Concept Communication Arrangement Management The provided sources do not contain enough grounded information to write a reliable 2–4 sentence definition for an **undefined** concept. Please supply a valid concept name and relevant source snippets so an accurate, source-grounded definition can be produced.