Setting Up an External Identity

Objective

After completing this lesson, you will be able to configure the interface between SAP Customer Data Cloud and an External ID Provider.

Connecting to an External ID Provider

​Integrating an external Identity Provider (IdP) with SAP Customer Data Cloud allows organizations to enable Single Sign-On (SSO) for members, making login across various platforms more seamless. ​

By connecting your SAP Customer Data Cloud to a centralized IdP, members can log into customer-facing applications using their existing organization credentials, enhancing security and simplifying access management. ​

This setup involves configuring SAML settings to establish trust between the Identity Provider and SAP Customer Data Cloud, acting as the Service Provider, ensuring a smooth authentication process.

To establish a secure connection between an external Identity Provider (IdP) and SAP Customer Data Cloud, metadata must be exchanged between the systems. This exchange is crucial for ensuring a trusted connection. In this case, metadata from the external IdP application must be entered in the settings of the Delegated Admin Console of the SAP Customer Data Cloud, as shown in the following screenshot:

This screenshot displays the External Identity configuration page for setting up SAML (Security Assertion Markup Language) Single Sign-On (SSO) in an application. It shows the fields where metadata retrieved from an external identity provider must be entered. The fields are named: Issuer, Single Sign On Service URL, Single Sign On Service Binding,Single Logout Service UR, Single Logout Service Binding, Name ID Format, x509 Certificate, and Certificate Signature Algorithm.
  • The Issuer is a unique identifier for the IdP.
  • The SSO Service URL is where the SP sends users to log in.
  • The Single Logout (SLO) URL allows users to log out from all connected services.
  • Service Bindings specify the attribute mapping used to transfer user data between the IdP and SP.
  • The NameID Format defines how users are identified, often using email or a unique identifier.
  • The Certificate and Signature Algorithm (e.g. RSA-SHA256) specifies the encryption used to secure the data exchange.

To complete the secure connection setup, you also need to export the metadata from the SAP Customer Data Cloud and import it into the external Identity Provider (IdP). The following screenshot shows where you can export the metadata from the Delegated Admin Console and pass it to the external IdP:

The screenshot shows the SP Metadata configuration section in the Delegated Admin Console of SAP Customer Data Cloud B2B Module. The screen shows fields for SAML metadata used to configure a secure transaction between an Identity Provider (IDP) and a Service Provider (SP), which is the Delegated Admin Console of the SAP Customer Data Cloud. For Certificate Signature Algorithm, the slide shows the value SHA1; for Metadata URL, a URL for accessing the service metadata; for Issuer, a URL representing the identity of the issuer; for Assertion Consumer Service URL, a URL for receiving authentication responses; for Single Logout Service URL, a URL provided for service logout operations, and for x509 Certificate, an encoded digital certificate Additional options are present but grayed out in the configuration, such as the Issuer field and various SAML bindings.

Log in to track your progress & complete quizzes