• Overview
  • Configuration

Backlog

How to configure Backlog extension in ADManager Plus

Identity ProvisioningProject Management

Integrating Backlog with ADManager Plus streamlines how user access is managed across your project management environment. By connecting Backlog with Active Directory through ADManager Plus, organizations can automate user provisioning and deprovisioning workflows, ensuring that the right users have the right level of access at the right time.

When a user joins, moves, or leaves the organization, ADManager Plus automatically creates, updates, or disables their Backlog account based on changes in Active Directory. This eliminates manual account handling, reduces administrative overhead, and minimizes the risk of orphaned or over-privileged accounts in Backlog.

 

Automate Backlog user lifecycle

Provision and deprovision accounts automatically from Active Directory via ADManager Plus.

 

Ensure timely access updates

Reflect onboarding, role changes, and offboarding instantly without manual effort.

 

Strengthen security and efficiency

Centralize identity-driven access management to reduce admin toil and eliminate stale accounts.

 

How to configure Backlog extension in ADManager Plus

Prerequisites:

Please ensure an API key with permissions is provided to retrieve desired information and perform tasks in Backlog. Refer to the Backlog's API references for more details.

Privileges

To import users from Backlog (inbound action): Ensure the account used for authorization has permission to read all user accounts.

To perform any action or query in Backlog (outbound Action): Ensure the account used for authorization has permission to perform the desired action.

Note: ADManager Plus comes with a preconfigured 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 Backlog API documentation to configure the inbound or outbound webhooks to perform the required actions.

Installing an integration in ADManager Plus

  • Log in to ManageEngine Marketplace
  • Under ADManager Plus, select Backlog.
  • Click the Download button to download the extension Zip file.
  • Log in to ADManager Plus and navigate to the Admin tab.
  • In the left pane, under Marketplace, click Extensions.
  • Navigate to the Install Extension tab in the top right.
  • In the Install Extension dialog, click Browse.
  • Select the downloaded .ext file from your local system.
  • Click Continue to Install to proceed with the installation.
  • Once the installation is complete, verify that the extension appears in the installed extensions list.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select Backlog.
  • Toggle the Enable Backlog Integration button to On.
  • In the Backlog Configuration page, click Authorization.
  • Enter the API Key generated from Backlog in the Authorization Value.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to synchronize user data from Backlog to ADManager Plus. The attribute mapping configured in this section can be selected as the data source during automation configuration. To configure an inbound webhook for Backlog:

  • Under Inbound Webhook, click Backlog Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, Backlog- Get All Users ENDPOINT and Get Projects ENDPOINT comes preconfigured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from Backlog. To use this preconfigured endpoint, replac e {UsersOrganization} w ith the Backlog space URL. However, if you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and fill in the required fields as per Backlog'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.
    • You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component.
    • Refer to Backlog's API references and configure additional headers and parameters, if required.
  • Once done, click Test and Save. A response window will display the r equested parameters that can be fetched using the API call. Click Proceed. Note:
    • Refer to Backlog's API references to learn the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Backlog 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 Backlog. Note: ADManager Plus also lets you customize attribute format from Backlog
  • 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. 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 attribute in Backlog.
    • If you would like to create a new custom format for this, click Add New Format.
    • 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 Backlog or fetch and forward required details from Backlog and synchronize them with AD. To configure an outbound webhook for Backlog:

  • Under Outbound Webhook, click Backlog 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 Backlog'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).