• Overview
  • Configuration

Ivanti

Align ITSM processes by integrating Ivanti tickets with directory actions.

Ticket managementITSM

Overview

Ivanti provides unified IT management solutions that combine endpoint management, security, service management, and identity capabilities. Its Neurons platform consolidates data across users, devices, and applications to drive automated IT operations and visibility. The People module within Ivanti stores and manages identity-related attributes that can be integrated with external systems. Connecting Ivanti with ADManager Plus allows organizations to synchronize user data from Ivanti to Active Directory (AD), enabling identity-driven automation across endpoint and directory systems.

Use cases

 

Automate user provisioning

Import user data from Ivanti’s People module into Active Directory to automate account provisioning.

 

Update user attributes

Reflect updates made to user records in Ivanti (e.g., manager, department, or work location) in corresponding AD attributes.

 

Trigger deprovisioning actions

Trigger deprovisioning actions in AD based on employee status or role changes recorded in Ivanti.

 

Prerequisites:

Please ensure to provide the bearer token to retrieve desired information and perform tasks in Ivanti. Refer to Ivanti API references for more details.

Privileges:

  • To import users (inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in Ivanti (outbound action): Ensure the account used for authorization has permission to perform the desired action.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select Ivanti.
  • Toggle the Enable Ivanti Integration button on.
  • In the Ivanti Configuration page, click Authorization.
  • Perform the steps to generate Bearer token in Ivanti and paste the Bearer token in the Value field.
  • Replace {X-ClientSecret}, {X-TenantId}, {X-ClientId} value in authorization endpoint's header values with that of your instance.
  • Click Configure.

Inbound webhook configuration

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

  • Under Inbound Webhook, click Ivanti Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, Ivanti GET ALL PEOPLE ENDPOINT, comes preconfigured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from Ivanti. 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 Ivanti’s API references. Click here to learn how. Note:
    • Authorization Header is preconfigured as a header for authenticating API requests as configured during Authorization Configuration.
    • Macros: You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component. Refer to Ivanti'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. After verifying if the requested parameters have been called to action, click Proceed. Note:
    • Refer to Ivanti’s API references to know the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Ivanti 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 Ivanti.
  • 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., id).
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in Ivanti.
    • 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 Ivanti or fetch or forward required details from Ivanti and synchronize them with AD. They can also be applied directly to desired users to perform a sequence of actions on them (Management > Advanced Management > Orchestration).

To configure an outbound webhook for Ivanti:

  • Under Outbound Webhook, click Ivanti 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 Ivanti’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 & Save.
  • A pop-up window will then display a list of AD users and groups on which to test the configured API call. Select the desired user or group on 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 according to 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).