ManageEngine Endpoint Central
Visualize Manage Engine computers, patches and remote offices in the JupiterOne graph. Our guide provides step-by-step instructions on setting up the integration gaining visibility to your ManageEngine Endpoint Central environment.
- Installation
- Data Model
- Types
Installation
To install this integration, you will need to configure settings both within ManageEngine Endpoint Central and on JupiterOne. Before enabling in JupiterOne, ensure that you complete the setup within your ManageEngine Endpoint Central's account.
Configuration on ManageEngine Endpoint Central
First, follow the table in the ManageEngine Endpoint Central documentation to get correct Zoho Account and Endpoint Central API URLs, as well link to the Zoho Developer Console necessary to the next steps.
ManageEngine Integration Setup Guide
This guide provides detailed, step-by-step instructions to set up an integration with ManageEngine Desktop Central. There are two integration options available: On-Premises and Cloud. Follow the instructions below to ensure your integration is configured correctly.
Table of Contents
Prerequisites
Before you begin, ensure you have:
- An active ManageEngine Desktop Central subscription.
- API access enabled and necessary credentials obtained.
- Basic knowledge of REST APIs and your current environment setup.
- Network/firewall settings that allow outbound API requests.
On-Premises Integration Setup
ManageEngine offers two methods for on-premises integration depending on your authentication method:
API Token Authentication
Access the On-Premises API Documentation
Familiarize yourself with the available endpoints and guidelines in the ManageEngine On-Premises API Documentation.Generate an API Token
- Log in to your Desktop Central instance.
- Navigate to Admin → Integrations → API Key Management.
- Create or regenerate your API token.
- If two factor is enabled make sure to complete the steps providing the OTP.
- Note: Ensure that this token remains confidential.
Configure Your Integration
- Update your JupiterOne integration settings. Select On-Premise Token Authentication.
- Input your Server URL and API Token.
Username/Password Authentication (No Two-Factor)
If you are not using two-factor authentication, you can also integrate using your username and password.
Review Authentication Requirements
- If two-factor authentication is disabled, you can use your ManageEngine username and password for integration.
- Consult the ManageEngine On-Premises API Documentation for details on the authentication endpoint.
Configure Your Integration
- Update your JupiterOne integration settings. Select On-Premise AD Authentication or On-Premise Local Authentication depending on your setup.
- Input your Server URL, username, password and domain if needed.
Cloud Integration Setup
Familiarize yourself with the cloud API by referring to the ManageEngine Cloud API Documentation.
Steps:
Log in to Zoho Developer Console
Access the Zoho Developer Console with your credentials.Create a "Self Client" Client Type
Create a new client of type "Self Client".Retrieve Client Credentials
- Navigate to the "Client Secret" tab.
- Copy the "Client ID" and "Client Secret" and save them somewhere secure.
Generate an Authorization Code
- Go to the "Generate Code" tab within your "Self Client" application.
- Set the Scope to:
DesktopCentralCloud.Common.READ,DesktopCentralCloud.SOM.READ,DesktopCentralCloud.Inventory.READ,DesktopCentralCloud.PatchMgmt.READ
- Optionally, set the Time Duration to 10 minutes.
- Provide a Scope Description (e.g., "JupiterOne Integration").
- Click Create to generate an authorization code.
Obtain the Refresh Token
Use the generated code in the following
curl
command (replace<code>
,<client_id>
, and<client_secret>
with your actual values):curl -X POST -H "Content-Type: application/x-www-form-urlencoded" \
-d "code=<code>&client_id=<client_id>&client_secret=<client_secret>&redirect_uri=https://www.zoho.com" \
https://accounts.zoho.com/oauth/v2/tokenThe response will include a JSON with the refresh token.
Save the Credentials
Store the "refresh token", along with your "Client ID" and "Client Secret", securely. These credentials will be needed later when configuring JupiterOne.
Support
For more details and assistance, refer to the official documentation:
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Computer | manageengine_computer | Device |
Patch | manageengine_patch | Finding |
RemoteOffice | manageengine_remote_office | Group |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
manageengine_computer | HAS | manageengine_patch |
manageengine_remote_office | MANAGES | manageengine_computer |
manageengine_remote_office | ENFORCES | manageengine_patch |
Manageengine Computer
manageengine_computer
inherits from Device
Property | Type | Description | Specifications |
---|---|---|---|
agentVersion | string | ||
assetTag | array of string s | ||
deviceName | string | ||
hardwareModel | string | ||
hardwareSerial | string | ||
hardwareVendor | string | ||
hardwareVersion | string | ||
id | string | ||
ipAddresses | array of string s | ||
macAddress | array of string s | ||
officeName | string | ||
platform | string | ||
status | string | ||
systemVersion | string | ||
type | string | ||
vendor | string | ||
version | string |