Chapter 67 Configuring SuccessFactors The following is an overview of the steps required to configure the SuccessFactors Enterprise Edition Web application for single sign-on (SSO) via SAML. SuccessFactors offers both IdP-initiated SAML SSO (for SSO access through the user portal or Centrify mobile applications) and SP-initiated SAML SSO (for SSO access directly through the SuccessFactors web application). You can configure SuccessFactors for either or both types of SSO. Enabling both methods ensures that users can log in to SuccessFactors in different situations such as clicking through a notification email. 1 Prepare SuccessFactors for single sign-on (see "SuccessFactors requirements for SSO" on page 67-14). 2 In the Centrify Cloud Manager, add the application and configure application settings. Once the application settings are configured, complete the user account mapping and assign the application to one or more roles. For details, see "Configuring SuccessFactors in Cloud Manager" on page 67-15. 3 Configure the SuccessFactors application for single sign-on. To configure SuccessFactors for SSO, contact SuccessFactors and give them the downloaded SAML Meta data file available from the Cloud Manager Application Settings page. For details, see "Contacting SuccessFactors to enable SSO" on page 67-20. After you are done configuring the application settings in the Cloud Manager and the SuccessFactors application, users are ready to launch the application from the Centrify user portal. 13
Preparing for SuccessFactors Configuration Preparing ring for SuccessFactors Configuration SuccessFactors requirements for SSO Before you configure the SuccessFactors web application for SSO, you need the following: An active SuccessFactors account with administrator rights for your organization. A signed certificate. You can either download one from Cloud Manager or use your organization s trusted certificate. Contact information for SuccessFactors configuration consultant (to enable and test the SSO feature on your account). Identity Provider SAML Meta data downloaded from the Centrify Cloud Manager. Setting up the certificates for SSO To establish a trusted connection between the web application and the cloud service, you need to have the same signing certificate in both the application and the application settings in Cloud Manager. If you use your own certificate, you upload the signing certificate and its private key in a.pfx or.p12 file to the application settings in Cloud Manager. You also upload the public key certificate in a.cer or.pem file to the web application. To download an application certificate from Cloud Manager (overview): 1 In the Apps page, add the application. 2 Click the application to open the application details. 3 In the Application Settings tab, click Download Signing Certificate to download and save the certificate. What you need to know k about SuccessFactors Each SAML application is different. The following table lists features and functionality specific to SuccessFactors. Capability Web browser client Supported? Yes Support details Mobile client Yes ios and Android SAML 2.0 Yes Chapter 67 Configuring SuccessFactors 14
Configuring SuccessFactors in Cloud Manager Capability SP-initiated SSO Yes Users may go directly to a supplied SuccessFactors URL and then use the Centrify identity platform SSO to authenticate. IdP-initiated SSO Yes Users may use SSO to log in to SuccessFactors through the Centrify user portal or through Centrify mobile apps. Force user login via SSO only Yes If SSO is enabled, logging in to SuccessFactors using a user name and password is not available. Separate administrator login after SSO is enabled User or Administrator account lockout risk Automatic user provisioning Self-service password Access restriction using a corporate IP range Supported? No Yes No N/A Yes Support details You need to consult with the SuccessFactors customer support team to set up your specific configuration. There is a risk of being locked out of your account if users are forced to log in using SSO only. As an administrator of the system, if you are locked out and SSO is enabled, you must call SuccessFactors to disable SSO temporarily to bypass the lockout. The SuccessFactorsConfiguration Consultant can setup Performance Manager to restrict access to a company instance using an IP Address or IP Range. Additionally, you can specify an IP Range in the Cloud Manager Policy page to restrict access to the application. Configuring SuccessFactors in Cloud Manager To add and configure the SuccessFactors application in Cloud Manager: 1 In Cloud Manager, click Apps. 2 Click Add Web Apps. The Add Web Apps screen appears. 3 On the Search tab, enter the partial or full application name in the Search field and click the search icon. 4 Next to the application, click Add. 5 In the Add Web App screen, click Yes to confirm. Cloud Manager adds the application. 6 Click Close to exit the Application Catalog. The application that you just added opens to the Application Settings page. Cloud Manager user s guide 15
Configuring SuccessFactors in Cloud Manager 7 Configure the following: Field Required or optional Set it to Consumer Service URL Required https:// performancemanager4. successfactors.com/ saml2/ SAMLAssertionConsume r?company=company- NAME Issuer Required The cloud service automatically generates the content for this field. Error URL Optional The cloud service automatically generates the content for this field. What you do If your fully qualified domain name (FQDN) is not the same as performancemanager4.suc cessfactors.com, replace it with the FQDN for your instance. In most cases, you can leave this field as is. The only reason to change this URL is if you are using multiple SuccessFactors deployments. Each deployment requires a unique Issuer. The Issuer content is automatically included as part of the Identity Provider SAML Meta data that you give to your SuccessFactors Configuration Consultant (see "Contacting SuccessFactors to enable SSO" on page 67-20). If you change the setting, you need to download the Identity Provider SAML Meta data again and give the file to the SuccessFactors Configuration Consultant. The Logout URL is automatically included as part of the Identity Provider SAML Meta data that you give to the SuccessFactors Configuration Consultant (see "Contacting SuccessFactors to enable SSO" on page 67-20). This custom page displays in the Centrify user portal when users encounter an error in SuccessFactors. If you change the setting, you need to download the Identity Provider SAML Meta data again and give the file to the SuccessFactors Configuration Consultant. Chapter 67 Configuring SuccessFactors 16
Configuring SuccessFactors in Cloud Manager Field Logout URL Optional The cloud service automatically generates the content for this field. Download Identity Provider SAML Meta data Required or optional Required Set it to The cloud service automatically generates the meta data content. Download Signing Certificate Required The cloud service automatically generates the meta data content. What you do The Logout URL is automatically included as part of the Identity Provider SAML Meta data that you give to the SuccessFactors Configuration Consultant (see "Contacting SuccessFactors to enable SSO" on page 67-20). Configuring Logout URL means that users are logged out of the Centrify user portal when they log out of SuccessFactors. Click the link to download the Meta data file. The SuccessFactors Configuration Consultant will need the file to enable SSO. See "Contacting SuccessFactors to enable SSO" on page 67-20. If necessary, click the link to download the default Signing Certificate. The certificate content is automatically included as part of the Identity Provider SAML Meta data. To use a certificate with a private key (pfx file) from your local storage, see Step 7 below. If you replace the certificate, download the Identity Provider SAML Meta data again and give the file to the SuccessFactors Configuration Consultant. Cloud Manager user s guide 17
Configuring SuccessFactors in Cloud Manager 8 On the Application Settings page, expand the Additional Options section and specify the following settings: Option Application ID Show in User app list Security Certificate Description Configure this field if you are deploying a mobile application that uses the Centrify mobile SDK, for example mobile applications that are deployed into a Samsung KNOX version 1 container. The cloud service uses the Application ID to provide single sign-on to mobile applications. Note the following: The Application ID has to be the same as the text string that is specified as the target in the code of the mobile application written using the mobile SDK. If you change the name of the web application that corresponds to the mobile application, you need to enter the original application name in the Application ID field. There can only be one SAML application deployed with the name used by the mobile application. The Application ID is case-sensitive and can be any combination of letters, numbers, spaces, and special characters up to 256 characters. Select Show in User app list to display this web application in the user portal. (This option is selected by default.) If this web application is added only to provide SAML for a corresponding mobile app, deselect this option so the web application won t display for users in the user portal. These settings specify the security certificate used for secure SSO authentication between the cloud service and the web application. Select an option to change the security certificate. Use existing certificate displays beneath it the certificate currently in use. The Download button below the certificate name downloads the current certificate through your web browser to your computer so you can supply the certificate to the web application during SSO configuration. It s not necessary to select this option it s present to display current status. Use the default tenant signing certificate selects the cloud service standard certificate for use. This is the default setting. Use a certificate with a private key (pfx file) from your local storage selects any certificate you want to supply, typically your organization s own certificate. To use this selection, you must click Browse to upload an archive file (.p12 or.pfx extension) that contains the certificate along with its private key. If the file has a password, you must enter it when prompted. 9 (Optional) On the Description page, you can change the name, description, and logo for the application. For some applications, the name cannot be modified. The Category field specifies the default grouping for the application in the user portal. Users have the option to create a tag that overrides the default grouping in the user portal. Chapter 67 Configuring SuccessFactors 18
Configuring SuccessFactors in Cloud Manager 10 On the User Access page, select the role(s) that represent the users and groups that have access to the application. When assigning an application to a role, select either Automatic Install or Optional Install: Select Automatic Install for applications that you want to appear automatically for users. If you select Optional Install, the application doesn t automatically appear in the user portal and users have the option to add the application. 11 (Optional) On the Policy page, specify additional authentication control for this application.you can select one or both of the following settings: Restrict app to clients within the Corporate IP Range: Select this option to prevent users outside the company intranet from launching this application. To use this option, you must also specify which IP addresses are considered as your intranet by specifying the Corporate IP range in Settings > Corporate IP Range. Require Strong Authentication: Select this option to force users to authenticate using additional, stronger authentication mechanisms when launching an application. Specify these mechanisms in Policy > Add Policy Set > Account Security Policies > Authentication. You can also include JavaScript code to identify specific circumstances when you want to block an application or you want to require additional authentication methods. For details, see Specifying application access policies with JavaScript. 12 On the Account Mapping page, configure how the login information is mapped to the application s user accounts. The options are as follows: Use the following Directory Service field to supply the user name: Use this option if the user accounts are based on user attributes. For example, specify an Active Directory field such as mail or userprincipalname or a similar field from the Centrify user service. Everybody shares a single user name: Use this option if you want to share access to an account but not share the user name and password. For example, some people share an application developer account. Use Account Mapping Script: You can customize the user account mapping here by supplying a custom JavaScript script. For example, you could use the following line as a script: LoginUser.Username = LoginUser.Get('mail')+'.ad'; The above script instructs the cloud service to set the login user name to the user s mail attribute value in Active Directory and add.ad to the end. So, if the user s mail attribute value is Adele.Darwin@acme.com then the cloud service uses Adele.Darwin@acme.com.ad. For more information about writing a script to map user accounts, see the SAML application scripting guide. Cloud Manager user s guide 19
Contacting SuccessFactors to enable SSO 13 (Optional) On the Advanced page, you can edit the script that generates the SAML assertion, if needed. In most cases, you don t need to edit this script. For more information, see the SAML application scripting guide. On the Changelog page, you can see recent changes that have been made to the application settings, by date, user, and the type of change that was made. Note 14 Click Workflow to set up a request and approval work flow for this application. The Workflow feature is a premium feature and is available only in the Centrify Identity Service App+ Edition. See Configuring Workflow for more information. 15 Click Save. After configuring the application settings (including the role assignment) and the application s web site, you re ready for users to launch the application from the user portal. Contacting SuccessFactors to enable SSO To configure SuccessFactors for SSO: 1 If you haven t done so already, locate the Identity Provider SAML Meta data that you downloaded in Step 7 of Configuring SuccessFactors in Cloud Manager. 2 Contact your SuccessFactors Configuration Consultant and provide the Identity Provider SAML Meta data you downloaded previously. Let the SuccessFactors Configuration Consultant know that the Centrify SAML Response has the assertion signed. Additionally, provide the following information (the configuration of these items is optional): Enable SP-initiated SSO for the account: If SP-initiated SSO is enabled, users log in to SuccessFactors using SAML (logging in with a user name and password is not available). If SP-initiated SSO is disabled, users log in to SuccessFactors using a user name and password. Users can SSO to SuccessFactors using SAML from the Centrify user portal. Error URL: Provide an error URL if you want users to be redirected to a custom page when they encounter an error in SuccessFactors. Logout URL: Provide a logout URL if you want users to be redirected to a specific URL upon logging out of SuccessFactors. Chapter 67 Configuring SuccessFactors 20
For more information about SuccessFactors For more information about SuccessFactors For more information about configuring SuccessFactors for SSO, contact your SuccessFactors representative. Cloud Manager user s guide 21
For more information about SuccessFactors Chapter 67 Configuring SuccessFactors 22