Organizations undergoing mergers, acquisitions, divestitures, or transition service agreement (TSA) periods often face the challenge of providing seamless access to the same SAP application for users belonging to different identity domains.
In our scenario, an SAP application hosted within Domain1 was already configured for SAML-based Single Sign-On with Microsoft Entra ID. The primary requirement was:
- Enable users from Domain2 to access the same SAP application using SAML SSO.
- Preserve the existing Domain1 SSO experience without any disruption.
- Avoid changes that could impact current production users.
- Provide automatic routing to the appropriate Identity Provider based on the URL used.
This blog explains how the SAP SAML 2.0 Multiple Identity Provider feature can be leveraged to achieve this requirement.
Read More Technology Blog Posts by Members articles
#abap