SAML Metadata Exchange
The concept name was not provided (marked as "undefined"), and the available source snippets do not contain enough substantive content to identify or define a specific SAP developer concept. Sources [S1] and [S2] reference SAP BTP trust configuration and SAML token signing key rotation, while [S3]–[S7] are tutorial titles only, providing no body text to draw from.
Without a named concept and with insufficient grounded source material, a compliant definition cannot be produced.
Tutorials that teach this
- Tutorial Connect Azure Active Directory to Identity Authentication Service
- Tutorial Establish Trust Configuration between SAP S/4HANA Cloud, public edition and SAP BTP Subaccount
- Tutorial Set Up Trust Between Identity Authentication and SAP Business Technology Platform Neo Environment
- Tutorial Establish Trust Configuration between SAP S/4HANA On-premise and SAP BTP
- Tutorial Set Up Trust Between SAP Cloud Identity Services and SAP BTP Subaccount
Docs explaining this concept
Prerequisites
- 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.