• Overview
  • Configuration

Peopleforce

Keep Peopleforce HR updates reflected in IT accounts without manual effort.

AD & HR syncHCM

Overview

Integrating PeopleForce with Active Directory through ADManager Plus allows organizations to automate identity management processes by connecting HR updates directly with IT provisioning. This ensures that every employee addition, update, or removal in PeopleForce is reflected accurately and promptly in Active Directory. By eliminating manual steps and syncing HR-driven events with AD, the integration helps accelerate onboarding, maintain up-to-date access rights, and ensure secure, policy-compliant offboarding.

 

Streamlined onboarding

Automatically provision AD accounts when new hires are added in PeopleForce, with pre-assigned roles and permissions.

 

Real-time access updates

Reflect team or designation changes instantly in AD to ensure access stays relevant as roles evolve.

 

Automated offboarding

Disable or remove AD accounts immediately when employees are offboarded in PeopleForce, reducing security risks.

 

Configuration Document: Integrating PeopleForce with ADManager Plus

Prerequisites:

Please ensure to provide an API key with permissions to retrieve desired information and perform tasks in Datadaog. Refer to PeopleForce's API references for more details.

Privileges:

  • To import users from PeopleForce (Inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in PeopleForce (Outbound Action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with pre-configured set of APIs that helps perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from PeopleForce API documentation to configure under inbound or outbound webhooks to perform the required actions.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select PeopleForce.
  • Toggle the Enable PeopleForce Integration button on.
  • In the PeopleForce Configuration page, click Authorization.
  • Perform the steps to generate the API Keys and API Token in PeopleForce and enter the API Key in the value field.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from PeopleForce to ADManager Plus. To configure an inbound webhook for PeopleForce:

  • Under Inbound Webhook, click PeopleForce Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, PeopleForce List All Employees ENDPOINT, comes pre-configured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from PeopleForce. If you would like to use this pre-configured endpoint, replace {id} with the domain name of your PeopleForce instance in the Endpoint URL field. However, if you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and filling in the required fields as per PeopleForce's API references. Click here to learn how. Note:
    • The API key value pair is preconfigured as a header for authenticating API requests, as configured during authorization configuration.
    • Macros: Explain about macros how they can use these to dynamically change the endpoint to meet their requirement.
    • Refer to PeopleForce's API references and configure additional headers and parameters, if required.
  • Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. Click Proceed. Note:
    • Refer to PeopleForce's API references to know the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for PeopleForce using the + Add API endpoint button. Click here to learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in PeopleForce.[ADManager Plus also lets you customize attribute format from PeopleForce]
  • Click + Add New Configuration and perform the following:
    • Enter the Configuration Name and Description and select the Automation Category from the drop-down menu.
    • In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g. employeeIdentifier).
      Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in PeopleForce.
    • If you would like to create a new custom format for this, click Mapping Attribute.
    • Click Save.
Note: The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response.

Outbound webhook configuration

Outbound webhook enables you to update the changes made in AD using ADManager Plus to PeopleForce or fetch/forward required details from PeopleForce and synchronize them with AD. To configure an outbound webhook for PeopleForce:

  • Under Outbound Webhook, click PeopleForce Webhook Configuration.
  • Click + Add Webhook.
  • Enter a name and description for this webhook.
  • Decide on the action that has to be performed and refer to PeopleForce's API references for the API details, such as the URL, headers, parameters, and other requirements that will be needed.
  • Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
  • Enter the endpoint URL.
  • Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
  • Click Test and Save.
  • A pop-up window will then display a list of AD users and groups to test the configured API call. Select the desired user or group over which this API request has to be tested and click OK. This will make a real time call to the endpoint URL, and the selected objects will be modified as per the configuration.
  • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
Note: The webhooks configured in this section can be included in Orchestration Templates, which can be used in event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (under Management > Advanced Management > Orchestration).