Human Capital Management Blog Posts by Members
Gain valuable knowledge and tips on SAP SuccessFactors HCM suite and human capital management market from member blog posts. Share your insights with a post of your own.
cancel
Showing results for 
Search instead for 
Did you mean: 
vinayakc123
Participant
1,634

Identity authentication to different Corporate Idp based on email domains in SuccessFactors

Requirements:

The SuccessFactors system has multiple legal entities with separate email domains. The business requirement is to use different corporate IDP for identity authentication of users based on different email domains used in the employee’s email.

Configuration steps:

Step 1: Create multiple user groups in Identity Authentication System (IAS) to store users of different companies with company domains.

vinayakc123_0-1724253280511.png

Step 2: Map users to different user groups (created in step 1) based on their email domains in Target System Identity Authentication System (IAS) as shown below

Here we would need to check only the text after ‘@’ in the user’s email hence, we would create a email regex attribute to store the substring of the email address in the format ‘@companydomain.com’

Create 2 email regex attribute to store email domains for company 1 and company 2.

Navigate to Identity Provisioning -> Target System -> Click on SAP Identity Authentication system -> Properties-> Click on Edit -> Click on Add then select standard -> Save

vinayakc123_1-1724253280513.png

email-regex = /^([a-zA-Z0-9._%-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,})$/

Mapping Transformation:

"condition": "$.email =~ %email-regex% || $.ExternalEmail[0] =~ %email-regex%"

Here, the condition is comparing only the email domain from the email address. Below is the link for the SAP help documentation regarding the Properties.

https://help.sap.com/docs/cloud-identity-services/cloud-identity-services/properties

Now, map the email regex attributes to corresponding user groups in the transformation mapping.

Navigate to Identity Provisioning -> Target System -> Click on SAP Identity Authentication system -> Transformation-> Click on Edit Code -> Update the below code in the user mapping section-> Save

vinayakc123_2-1724253280517.png

           {

                "condition": "$.emails[0].value =~ %ias.email.domain.company1.regex.attribute%",

                "constant": "SSO_Company1",

                "targetPath": "$.groups[0].value"

            },

           {

                "condition": "$.emails[0].value =~ %ias.email.domain.company2.regex.attribute%",

                "constant": "SSO_Company2",

                "targetPath": "$.groups[0].value"

            }

Step 3: Configure Corporate Identity Providers in Identity Authentication System

Under Identity Providers, choose the Corporate Identity Providers

vinayakc123_3-1724253280518.png

Create new identity providers and give a display name. Update Identity Provider Type = Microsoft ADFS/Entra ID (SAML 2.0) and Click on the Create button.

vinayakc123_4-1724253280519.png

 

vinayakc123_5-1724253280520.png

Click on Company1 Azure AD and go to SAML Click on Application, Go to Trust -> SAML 2.0 Configuration, and click on Browse to upload the Metadata XML file of the Company1 Azure AD. Click Save.

Repeat the steps for Company2 Azure AD.

vinayakc123_6-1724253280525.png

Enable Identity Authentication user store under Identity Federation.

Repeat the steps for Company2 Azure AD.

vinayakc123_7-1724253280533.png

Step 4: Configuration of Conditional Authentication Rules

Navigate to Applications & Resources -> Applications -> Click on SAP SuccessFactors system -> Conditional Authentication

vinayakc123_8-1724253280538.png

Click on Add rule to create Conditional Authentication rules.

vinayakc123_9-1724253280539.png

Select the Corporate Idp of Company1 and the corresponding user group. Repeat the steps for Company 2 as well.

vinayakc123_10-1724253280542.png

This will enable users in SSO_Company1 to be redirected to Company1 Azure AD and users in SSO_Company2 to be redirected to Company 2 Azure AD respectively and any other users will be authenticated with IAS since it is the default Authentication Identity provider.

vinayakc123_11-1724253280545.png

Conclusion: The above steps can be replicated for additional user groups and Corporate IDp as per business requirements.

Also, the emails can be restricted to these email domains from IAS and emails can be triggered only to external users alone as well.

Hope this helps!

Happy Learning

2 Comments
Labels in this area