- Created by Phillip Hanegan, last modified on Jul 29, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 4 Next »
Connecting EmpowerID to your SAP SuccessFactors Employee Central module allows you to automate your Joiner, Mover, and Leaver functions seamlessly. This article provides the information you need to configure bidirectional usage of SuccessFactors in EmpowerID either as a managed resource or a source of identity data. You can use this connector to manage both users and employees.
Prerequisites
To connect EmpowerID to SuccessFactors, Read
permissions for the following SuccessFactors objects along wih their mentioned attributes are required:
Object | Attributes |
---|---|
PerPerson |
|
homeAddressNavDEFLT |
|
EmploymentNav |
|
JobInfoNav |
|
CompanyNav | Name_en_US |
CostCenterNav | CostCenterDescription |
EmployeeStatusNav | Status |
PersonalInfoNav |
|
PhoneNav |
|
EmailNav |
|
StateNav | ExternalCode |
Procedure
Step 1 – Generate a self-signed certificate in EmpowerID
Expand Apps and Authentication > SSO Connections on the EmpowerID Web interface's navbar and select SSO Components.
Select the Certificates tab and click the Add button in the grid header.
Select Generate Self-Signed Certificate.
Enter the following information:
Certificate Owner – Leave empty
Prefer Local Machine Store – Leave empty
Subject Name – Enter something suitable to the purpose of the certificate, such as CN=AzureCertificate
Requires Password – Select this option; this adds a private key to the certificate
Certificate Password – Enter a password for the certificate
Click Save to create the certificate.
Step 2 – Download the certificate in Base64 format
From the Certificate Details page, return to the SSO Components page by clicking the Find Certificates breadcrumb.
On the SSO Components page, select the Certificates tab and search for the certificate you just created.
Click the Name link for the certificate to navigate to the View page for the certificate.
On the View page for the certificate, click Export Certificate.
Select the desired location to save the certificate and click Save.
Step 3 – Register a service principal application in Entra ID
Log in to your Azure portal as a user with the necessary permissions to create an application in Entra ID.
In Azure, navigate to your Microsoft Entra ID.
Navigate to Manage > App registrations and click New registration.
Name the application, select the scope for the application (single or multitenant), and click Register.
Once the application is registered, copy the Application (client) ID and Directory (tenant) ID from the Overview page. These values are used when configuring the SCIM app service.
Navigate to the Certificates & secrets blade for the application and click Upload certificate.
Select the base-64 encoded certificate you downloaded from EmpowerID and click Add.
The public key certificate that you upload to Azure must have a corresponding private key in the EmpowerID certificate store; otherwise, an error will occur when calling Azure’s API.
Step 4 – Create an app service to host the SuccessFactors SCIM microservice
Log in to your Azure portal as a user with the necessary permissions to create an App Service.
In Azure, navigate to All Services > App Services and create a new App service.
Under Project Details, select a Subscription and then create a Resource Group for the App Service.
Under Instance Details, do the following:
Name – Enter a name.
Publish – Select Code.
Runtime Stack – Select .Net Core 8.
Operating System – Select Linux.
Region – Select the appropriate region.
Click Review + Create.
Click Create.
After the deployment of the app service completes, click Go to resource.
Change the platform for the app service to 64 Bit by doing the following:
On the app service navbar, under Settings, click Configuration.
On the Configuration blade, select the General settings tab.
Under Platform settings, change the Platform to 64 Bit and click Save.
Click Continue to confirm you want to save the changes.
Copy and save the URL on the app service's overview page. You will need it when configuring Entra ID Auth for the app service.
Step 5 – Configure authentication for the app service
Navigate to Settings > Authentication and click Add identity provider.
Select Microsoft.
Add the following identity provider information:
Choose a tenant for your application and its users – Select Workforce configuration (current tenant)
App registration type – Select Pick an existing app registration in this directory.
Name or app ID – Select the service principal application you created to provide Entra ID authentication for the microservice.
Issuer URL – Replace the default value with
https://login.microsoftonline.com/<Your Tenant ID>
Client application requirement – Select Allow requests only from this application itself
Identity Requirement – Select Allow requests from any identity
Tenant requirement – Select Allow requests from specific tenants
Allowed tenants – Ensure the Tenant ID matches the specific tenant
Restrict access – Select Require authentication.
Unauthenticated requests – Select HTTP 401 Unauthorized: recommended for APIs.
Token Store – Leave selected.
Click Add.
After adding the Identity provider, click the Edit link.
Set the Issuer URL to
https://login.microsoftonline.com/<Your Tenant ID>
.Under Allowed token audiences, enter the URL for the app service.
Click Save.
Under Settings, select Identity.
Turn on system assigned managed identity and click Save.
Click Yes to confirm you want to enable system assigned managed identity and register the App Service with Azure Active Directory.
Go to the App Service Overview page and click Download publish profile. You will need this file when you publish the SuccessFactors microservice to Azure.
Step 6 – Publish the SuccessFactors Microservice to Azure
Prior to publishing the microservice, you will need to obtain the appropriate ZIP file from EmpowerID.
Copy the below PowerShell script into the text editor of your choice and save it as
zipdeploy_appService.ps1
.param( $pubProfileFilePath ,$zipFilePath ) $ErrorActionPreference = "Stop" $pubProfile = [xml](gc $pubProfileFilePath) $zipPubProfile = $pubProfile.publishData.publishProfile | where { $_.publishMethod -eq "zipdeploy" } $userAgent = "powershell/1.0" $base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $zipPubProfile.userName, $zipPubProfile.userPWD))) $zipdeployUrl = "https://$($zipPubProfile.publishUrl)/api/zipdeploy" $deploymentsUrl = "https://$($zipPubProfile.publishUrl)/api/deployments" Invoke-RestMethod -Uri $zipdeployUrl -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)} -UserAgent $userAgent -Method Post -InFile $zipFilePath Invoke-RestMethod -Uri $deploymentsUrl -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)} -UserAgent $userAgent -Method Get
Open an administrative PowerShell session.
Navigate to the directory where you saved the script and execute the script, passing in the values of the
pubProfilePath
andzipFilePath
parameters via the command line, where the value ofpubProfilePath
is the path to the SuccessFactors App Service Publisher Profile Settings file you downloaded from Azure, and the value ofzipFilePath
is the path to the microservice ZIP file you received from EmpowerID.The command to execute the script should look similar to that shown in the below image.
Step 7 – Create an account store for SuccessFactors
On the navbar, expand Admin > Applications and Directories and select Account Stores and Systems.
Select the Actions tab and then click Create Account Store.
Under System Types, search for Success Factor Scim.
Click the record for Success Factor Scim Connector to select the type and then click Submit.
This opens the Success Factor SCIM form.Enter the following information in the SuccessFactors SCIM form:
Account Store Name – Name of the account store
App Service Base URL – The URL to the app service hosting the SuccessFactors SCIM microservice
WAITING FOR INFO TO COMPLETE
When ready, click Submit to create the account store.
Step 7 – Verify resource system parameters
Return to the Find Account Stores page and search for the SuccessFactors account store you just created.
Click the Account Store link.
Select the Resource System tab and then expand the Configuration Parameters accordion at the bottom of the page.
Verify the following parameters have the correct value:
AzureAppID
AzureTenantID
certificateThumbprint
GetNewOrUpdatedUsersUrl
MicroserviceUrl
Step 8 – Configure Attribute Flow
On the Account Store Details page for the Workday account store, select the Attribute Flow Rules tab.
Review the attribute flow and revise as needed. EmpowerID translates the attributes in Workday to SCIM for use with the connector and represents those attributes in EmpowerID as External Directory Attributes. You map these attributes to EmpowerID Person attributes to ensure that any changes occurring to user attributes in Workday flow to the EmpowerID Person, as well as any other user accounts owned by the Person.
To change the score for any of the available CRUD operations (Create, Update and Delete), enter the new score in the appropriate field. By default, scores are weighted evenly, which means that a change to an attribute originating in one connected external directory has the same authority as a change to an attribute occurring in another connected external directory.
Step 9 – Create Dynamic Hierarchy policies to generate roles and location (Optional)
If desired, you can use Dynamic Hierarchy policies to generate external roles and locations based on specific user attributes, such as Job Title
and Department
. The external roles and locations can then be used to map corresponding EmpowerID logical locations. Please see Use Dynamic Hierarchy Policies to Create External Roles and Locations for information on setting this up. When completed, return to this article and complete steps 10 and 11.
Step 10 – Configure the SuccessFactors account store
Click the Edit link on the Account Store Details page for the SuccessFactors account store to put the account store in Edit mode.
Edit the settings shown below as needed and save your changes.
Account Store Settings |
---|
Account Store Settings | |
---|---|
Setting | Description |
Authentication and Password Settings | |
Password Manager Policy for Accounts without Person | Specifies the Password Manager Policy to be used for user accounts not joined to an EmpowerID Person. |
Provisioning Settings | |
Allow Person Provisioning (Joiner Source) | Specifies whether EmpowerID Persons can be provisioned from user accounts in the account store. |
Allow Attribute Flow | Specifies whether attribute changes should flow between the account store and EmpowerID. |
Allow Provisioning (By RET) | Allows or disallows the Resource Entitlement (RET) Inbox process to auto-provision accounts for this domain for users who receive RET policy-assigned user accounts, but have not yet had them provisioned. |
Allow Deprovisioning (By RET) | Allows or disallows the Resource Entitlement Inbox process to auto de-provision accounts for this domain for users who still have RET policy-assigned user accounts, but no longer receive a policy that grants them a user account in the domain. De-provisioning only occurs if the de-provision action on the Resource Entitlement policy is set to De-Provision. |
Max Accounts per Person | This specifies the maximum number of user accounts from this domain that an EmpowerID Person can have linked to them. This prevents the possibility of a runaway error caused by a wrongly configured Join rule. It is recommended that this value be set to 1 unless users will have more than 1 account and you wish them to be joined to the same person. |
Business Role Settings | |
Allow Business Role and Location Re-Evaluation | Specifies whether Business Role and Location re-evaluation should occur for the account store |
Business Role and Location Re-Evaluation Order | This is an optional policy setting that can be used by provisioning workflows to determine which Account Store has priority when determining the roles and locations that should be assigned to a person. Account Stores with a higher value take precedence. |
Inventory Auto Provision OUs as IT System Locations | Specifies whether OUs in the external system are added as IT System locations in EmpowerID. If true, the OUs appear under the All IT Systems location node. |
Inventory Auto Provision External Roles as Business Roles | Specifies whether EmpowerID should provision Business roles for external account store roles If you are using Dynamic Hierarchy policies to generate custom external roles and locations, this options should be left disabled. |
Default Person Business Role | Specifies the default EmpowerID Business Role to be assigned to each EmpowerID Person provisioned from the user accounts in the account store. |
Default Person Location (leave blank to use account container) | Specifies the default EmpowerID Location to be assigned to each EmpowerID Person provisioned from the user accounts in the account store. |
Special Use Settings | |
Automatically Join Account to a Person on Inventory (Skip Account Inbox) | Specifies whether EmpowerID should attempt to join user accounts in the account store to an existing EmpowerID Person during the inventory process. When enabled, the Account Inbox is bypassed. |
Automatically Create a Person on Inventory (Skip Account Inbox) | Specifies whether EmpowerID should create new EmpowerID Persons from the user accounts discovered in the account store during the inventory process. When enabled, the Account Inbox is bypassed. |
Inventory Settings | |
Inventory Schedule Interval | Specifies the time span that occurs before EmpowerID performs a complete inventory of the account store. The default value is 10 minutes. |
Inventory Enabled | Allows EmpowerID to inventory the user information in the account store. |
Step 11 – Enable Inventory on the account store
On the Account Store Settings page, select the Inventory tab.
Change the Inventory Schedule Interval as needed. By default, EmpowerID inventories account stores once every 10 minutes.
Toggle Inventory Enabled.
Click Save to save your changes to the account store.
Now that inventory is enabled for the account store, the next step is to turn on the Account Inbox permanent workflow. This workflow is responsible for fetching and processing new user accounts.
Step 12 – Enable the Account Inbox Permanent Workflow
On the navbar, expand Infrastructure Admin > EmpowerID Server and Settings and select Permanent Workflows.
On the Permanent Workflows page, click the Display Name link for Account Inbox.
On the Permanent Workflow Details page that appears, click the pencil icon to put the workflow in edit mode.
Check Enabled.
Click Save to save your changes.
Step 13 - Map Role and Locations
On the navbar, expand Identity Lifecycle and select Role and Location Mapper.
Select the Role Mapper tab.
In the External Source Business Role pane of the Role Mapper tab, do the following:
In the first (upper) field - Search for and select the external directory containing the role you want to map, and
In the second (lower) field - Enter the name of the external role you want to map and press ENTER to load the role.
Select the role from the tree.
Select the Location Mapper tab.
In the External Source Location pane of the Location Mapper tab, do the following:
In the first (upper) field - Search for and select the external directory containing the location you want to map and
In the second (lower) field - Enter the name of the external location you want to map and press ENTER to load the location.
Select the location from the tree.
In the Internal Destination Location pane, enter the name of the EmpowerID location to which you want to map the external directory location and then select the location from the tree.
Click Save to save the mapping.
Repeat for any other mappings you wish to create.
If you select an external role or an external location that is a parent role or location, the children of that role or location will be mapped to the selected EmpowerID location.
Use Dynamic Hierarchy Policies to Create External Roles and Locations
IN THIS ARTICLE
- No labels