SAML 2.0 Metadata Exchange Between Service Provider and Identity Provider
Tutorials that teach this
- Tutorial Access Protected SAP Analytics Cloud Resources with OAuth Two-Legged Flow
- Tutorial Establish Trust Configuration between SAP S/4HANA Cloud, public edition and SAP BTP Subaccount
- 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
- Tutorial Reconfigure Trust Relationships on SAP HANA XS Systems
- Tutorial Create a Live Connection Between SAP HANA Cloud and SAP Analytics Cloud
- Tutorial Connect Azure Active Directory to Identity Authentication Service
- Tutorial Set Up Trust Between Identity Authentication and SAP Business Technology Platform Neo Environment
Code samples embodying this
Prerequisites
- Concept SAML 2.0 and OpenID Connect Identity Provider Trust SAML 2.0 and OpenID Connect Identity Provider Trust enables [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 so that users authenticated by a trusted identity provider can access protected resources. A developer uses it to establish trust and federation between an identity provider and the User Account and Authentication (UAA) service, allowing business users to log in via an external SAML or OpenID Connect identity provider. Default federation attributes, such as those [configured for SAML identity providers](https://help.sap.com/docs/btp/sap-business-technology-platform/6d073332bc5743fdb7f7f06bde499ab7?locale=en-US&state=PRODUCTION&version=Cloud), control how identity information is mapped and shared between the systems.
- Concept SAP Identity Authentication Service (IAS)
- Concept SAML 2.0 Configuration SAML 2.0 Configuration is the process of establishing a trust relationship between a Neo account acting as a SAML Service Provider and an external Identity Provider, enabling federated authentication for SAP BTP applications. Developers use it to [configure the Neo account as a SAML Service Provider and export its SAML metadata](https://help.sap.com/docs/btp/sap-business-technology-platform/107f1caecc554e3998b630d717276b48?locale=en-US&state=PRODUCTION&version=Cloud), as well as to [export the SAML metadata of the Identity Provider](https://help.sap.com/docs/btp/sap-business-technology-platform/5c1479e836c7411cba5f9ec1fdfba369?locale=en-US&state=PRODUCTION&version=Cloud) so that both parties can mutually recognize each other. This setup also involves creating a Neo application as a trusted Service Provider, allowing the application to participate securely in the SAML 2.0 authentication flow.