Tutorial: Azure Active Directory single sign-on (SSO) integration with SuccessFactors
In this tutorial, you'll learn how to integrate SuccessFactors with Azure Active Directory (Azure AD). When you integrate SuccessFactors with Azure AD, you can:
- Control in Azure AD who has access to SuccessFactors.
- Enable your users to be automatically signed-in to SuccessFactors with their Azure AD accounts.
- Manage your accounts in one central location - the Azure portal.
To get started, you need the following items:
- An Azure AD subscription. If you don't have a subscription, you can get a free account.
- SuccessFactors single sign-on (SSO) enabled subscription.
In this tutorial, you configure and test Azure AD SSO in a test environment.
- SuccessFactors supports SP initiated SSO.
Adding SuccessFactors from the gallery
To configure the integration of SuccessFactors into Azure AD, you need to add SuccessFactors from the gallery to your list of managed SaaS apps.
- Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
- On the left navigation pane, select the Azure Active Directory service.
- Navigate to Enterprise Applications and then select All Applications.
- To add new application, select New application.
- In the Add from the gallery section, type SuccessFactors in the search box.
- Select SuccessFactors from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
Alternatively, you can also use the Enterprise App Configuration Wizard. In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.
Configure and test Azure AD SSO for SuccessFactors
Configure and test Azure AD SSO with SuccessFactors using a test user called B.Simon. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in SuccessFactors.
To configure and test Azure AD SSO with SuccessFactors, perform the following steps:
- Configure Azure AD SSO - to enable your users to use this feature.
- Configure SuccessFactors SSO - to configure the Single Sign-On settings on application side.
- Create SuccessFactors test user - to have a counterpart of B.Simon in SuccessFactors that is linked to the Azure AD representation of user.
- Test SSO - to verify whether the configuration works.
Configure Azure AD SSO
Follow these steps to enable Azure AD SSO in the Azure portal.
In the Azure portal, on the SuccessFactors application integration page, find the Manage section and select Single sign-on.
On the Select a Single sign-on method page, select SAML.
On the Set up Single Sign-On with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, perform the following steps:
a. In the Sign-on URL textbox, type a URL using one of the following patterns:
b. In the Identifier textbox, type a URL using one of the following patterns:
c. In the Reply URL textbox, type a URL using one of the following patterns:
These values are not real. Update these values with the actual Sign-on URL, Identifier and Reply URL. Contact SuccessFactors Client support team to get these values.
On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, find Certificate (Base64) and select Download to download the certificate and save it on your computer.
On the Set up SuccessFactors section, copy the appropriate URL(s) based on your requirement.
Create an Azure AD test user
In this section, you'll create a test user in the Azure portal called B.Simon.
- From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
- Select New user at the top of the screen.
- In the User properties, follow these steps:
- In the Name field, enter
- In the User name field, enter the firstname.lastname@example.org. For example,
- Select the Show password check box, and then write down the value that's displayed in the Password box.
- Click Create.
- In the Name field, enter
Assign the Azure AD test user
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to SuccessFactors.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select SuccessFactors.
- In the app's overview page, find the Manage section and select Users and groups.
- Select Add user, then select Users and groups in the Add Assignment dialog.
- In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
- If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
- In the Add Assignment dialog, click the Assign button.
Configure SuccessFactors SSO
In a different web browser window, log in to your SuccessFactors admin portal as an administrator.
Visit Application Security and native to Single Sign On Feature.
Place any value in the Reset Token and click Save Token to enable SAML SSO.
This value is used as the on/off switch. If any value is saved, the SAML SSO is ON. If a blank value is saved the SAML SSO is OFF.
Native to below screenshot and perform the following actions:
a. Select the SAML v2 SSO Radio Button
b. Set the SAML Asserting Party Name(for example, SAML issuer + company name).
c. In the Issuer URL textbox, paste the Azure AD Identifier value which you have copied from the Azure portal.
d. Select Assertion as Require Mandatory Signature.
e. Select Enabled as Enable SAML Flag.
f. Select No as Login Request Signature(SF Generated/SP/RP).
g. Select Browser/Post Profile as SAML Profile.
h. Select No as Enforce Certificate Valid Period.
i. Copy the content of the downloaded certificate file from Azure portal, and then paste it into the SAML Verifying Certificate textbox.
The certificate content must have begin certificate and end certificate tags.
Navigate to SAML V2, and then perform the following steps:
a. Select Yes as Support SP-initiated Global Logout.
b. In the Global Logout Service URL (LogoutRequest destination) textbox, paste the Sign-Out URL value which you have copied form the Azure portal.
c. Select No as Require sp must encrypt all NameID element.
d. Select unspecified as NameID Format.
e. Select Yes as Enable sp initiated login (AuthnRequest).
f. In the Send request as Company-Wide issuer textbox, paste Login URL value which you have copied from the Azure portal.
Perform these steps if you want to make the login usernames Case Insensitive.
a. Visit Company Settings(near the bottom).
b. Select checkbox near Enable Non-Case-Sensitive Username.
c. Click Save.
If you try to enable this, the system checks if it creates a duplicate SAML login name. For example if the customer has usernames User1 and user1. Taking away case sensitivity makes these duplicates. The system gives you an error message and does not enable the feature. The customer needs to change one of the usernames so it’s spelled different.
Create SuccessFactors test user
To enable Azure AD users to sign in to SuccessFactors, they must be provisioned into SuccessFactors. In the case of SuccessFactors, provisioning is a manual task.
To get users created in SuccessFactors, you need to contact the SuccessFactors support team.
In this section, you test your Azure AD single sign-on configuration with following options.
Click on Test this application in Azure portal. This will redirect to SuccessFactors Sign-on URL where you can initiate the login flow.
Go to SuccessFactors Sign-on URL directly and initiate the login flow from there.
You can use Microsoft My Apps. When you click the SuccessFactors tile in the My Apps, this will redirect to SuccessFactors Sign-on URL. For more information about the My Apps, see Introduction to the My Apps.
Once you configure the SuccessFactors you can enforce session controls, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session controls extends from Conditional Access. Learn how to enforce session control with Microsoft Defender for Cloud Apps.