- Overview
- Configuration
Rootly
Streamline incident management with Rootly-AD synchronization
Rootly is an incident management platform that helps organizations streamline and standardize their incident response processes. Integrating Rootly with ManageEngine ADManager Plus streamlines incident management processes by automating incident creation and updates directly from ADManager Plus. This ensures real-time incident tracking, faster response times, and secure access controls, reducing administrative workload and improving efficiency.
Streamlined incident creation
IT admins can set Rootly to automatically log incidents based on user events in ADManager Plus, like failed login attempts or account status changes.
Need assistance to integrate Workable with ADManager Plus?
How to configure Rootly integration in ADManager Plus
Prerequisites
Please provide the Bearer toke n to retrieve the information you need and perform tasks in Rootly. Refer to Rootly's documentation onAPIs for more details.
Privileges
To import incidents (inbound action): Ensure the account used for authorization has permission to read all user accounts.
To perform any action or query in Rootly (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 to help perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from the Rootly API documentation to configure 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 for and select Rootly.
- Toggle the Enable Rootly Integration button on.
- In the Rootly Configuration page, click Authorization.
- Perform the steps to generate a earer token in Rootly and paste the Bearer token in the Value field.
- Click Configure.
Inbound webhook configuration
Inbound webhook enables you to fetch user data from Rootly 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 Rootly:
- Under Inbound Webhook, click Rootly Endpoint Configuration.
- In the Endpoint Configuration tab, an endpoint, Rootly USERS ENDPOINT, comes pre-configured with Endpoint URL, API Method, Headers, and Parameters fields to fetch incidents from Rootly .
- The API key-value pair 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 Rootly's API references and configure additional headers and parameters, if required.
- 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.
- Refer to Rootly's API references to know which Parameters must be configured to fetch only specific parameters.
- You can configure multiple endpoints for Rootly 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 Rootly.
- 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 (for example, 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 attribute in Rootly. If you would like to create a new custom format for this, click Add New Format.
- Click Save.
Note:
Note:
Outbound webhook configuration
Outbound webhook enables you to send changes made in AD to Rootly and carry out tasks in Rootly—all from ADManager Plus. The webhooks configured in this section can be included in Orchestration Templates, which in turn can be used during event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (Management > Advanced Management > Orchestration).
To configure outbound webhooks for Rootly:
- Under Outbound Webhook, click Rootly Webhook Configuration.
- Click + Add Webhook.
- Enter a name and description for this webhook.
- Decide which action has to be performed. Refer to Rootly'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.
