The integration was either created by Saviynt or by Saviynt community users . The integration is available “as is” and fall under standard connectors support for REST, SOAP, JDBC, LDAP, PowerShell, Jar and Saviynt Connector Framework.
Note: Contributor - Manju Kumari
This guide describes the integration between Saviynt Enterprise Identity Cloud (EIC) and NinjaOne.
This guide is intended for administrators and target application integration teams responsible for implementing a secure integration service with NinjaOne for RPA.
NinjaOne is a leading unified IT management software company that simplifies how IT teams work. MSPs and IT departments can automate, manage, and remediate all their device management tasks within one fast, modern, intuitive platform, improving technician efficiency and user satisfaction.
"NinjaOne" is a cybersecurity platform and product developed by the cybersecurity company NinjaRMM. NinjaRMM specializes in providing remote monitoring and management (RMM) solutions for IT professionals and managed service providers (MSPs).
Ticketing System: Users can create and manage support tickets to track customer issues and requests. Tickets can be assigned to specific agents or teams for resolution.
For more information about different connectors in EIC, see Connectors Documentation.
The NinjaOne integration supports the following features:
Release v4.5 and later
You must create an integration between EIC and the collaboration platform hosted by the target application to perform import, provisioning, and deprovisioning tasks. The following components are involved in the integration:
The Complete Service Management platform NinjaOne combines ITSM with ESM and SIAM capabilities, enabling all internal departments, such as IT, HR, and Facilities, as well as external service providers and customers, to collaborate securely and seamlessly on one complete platform, reducing complexity and improving productivity.
Objects are imported as entitlement types into EIC.
Security System represents the connection between EIC and the target application.
It comprises of an endpoint, which is the target application for which you want EIC to manage the identity repository.
It provides application instance abstraction from connectivity including high-level metadata. For more information about creating a security system, see Creating a Security System.
Endpoint is an instance of an application within the context of a security system.
It is the target application or application from which the connector imports the data and performs provisioning or deprovisioning of identity objects, such as users, accounts, and entitlements.
It is mandatory to create an endpoint after creating the security system.
You can associate a single security system with multiple endpoints if the deployment involves modelling of multiple isolated virtual applications (based on sets of specific entitlements according to certain categories) within a single application instance. For more information about creating an endpoint, see Creating an Endpoint for the Security System.
Connector is a software component that enables communication between EIC and the target application. It provides a simplified integration mechanism where in some instances you only need to create a connection with minimal connectivity information for your target application. The REST connector is used for importing, provisioning accounts and access through the REST APIs. For more information about creating a connection, see Creating a Connection.
Job Scheduler is a software component that executes a job based on the configured schedule to perform import or provisioning operations from EIC.
When a provisioning job is triggered, it creates provisioning tasks in EIC. When these tasks are completed, the provisioning action is performed on the target application through the configured connector. If you want to instantly provision requests for completing the tasks without running the provisioning job, you must enable Instant Provisioning at the security system level and the Instant Provisioning Tasks global configuration. For more information about the jobs used by the connectors in the NinjaOne integration.
EIC uses a REST connection for integrating with NinjaOne for performing provisioning items in NinjaOne Queue. The REST connection uses the REST protocol to communicate with the REST interface of NinjaOne.
The following diagram illustrates the integration architecture and communication with the target application.
Authentication to NinjaOne is through an Access Token please follow below steps.
A refresh token is a special kind of token used to obtain a renewed access token. You can request new access tokens until the refresh token expires. Applications must store refresh tokens securely because they essentially allow a user to remain authenticated forever.
2. Get Refresh Tokens
When registering an application sure your application's Grant Types include Refresh Token. Then you must include the offline_access scope when you initiate an authentication request through the /oauth/authorize endpoint.
You should only ask for a new token if the access token has expired. It's bad practice to call the endpoint to get a new access token every time you call an API.
To exchange the refresh token you received during authorization for a new access token, make a POST request to the /oauth/token endpoint, using grant_type=refresh_token.
Connection refers to the configuration setup for connecting EIC to target applications. For more information about the procedure to create a connection, see Creating a Connection.
While creating a connection, you must specify connection parameters that the connector uses to connect with the target application, define the type of operations to perform, the target application objects against which those operations are performed, and the frequency of performing them. In addition, you can view and edit attribute mappings between EIC and the target application, predefined correlation rules, and provisioning jobs and import jobs.
The connector uses the following parameters for creating a connection and for importing account and access from the target application:
Connection Name *
Provides a unique name for the connection.
Connection Description *
Provides the description for the new connection being created.
Connection Type *
Select the connection type as REST.
Allows you to save the connection template with the specified parameter values.
Click Save Template and specify the template name.
Provides the email template applicable for notifications.
Email notifications provides immediate trigger of emails to respective user based on actions performed. Emails acts as one of the notifications to user informing which action has been performed and if critical, needs immediate action from the user.
Default SAV Role
Provides the SAV role for which you want to assign access to the newly created connection.
The SAV role is a EIC Role used to give specific access to a User. For example, if ROLE_User is selected then user(s) assigned the ROLE_User are given access to this connection.
Specify this parameter to establish a REST connection with NinjaOneapplication.
To create Queue in NinjaOne, poll and fetch the status of Queue when WSRETRY job is run, specify the below mentioned parameters.
Specify this parameter to create Queue in NinjaOne.
When you run the WSRETRY job using the CREATETICKETJSON parameter, it creates Queue in NinjaOne. The possible status of Queue in NinjaOneare: Open, Closed, or Pending. The ticket remains in Open status in NinjaOne it is automatically or manually completed in NinjaOne.
connection package helps you build the connection with pre-defined JSONs, this can be used if your tenant does not already have out of the box connection templates available. Here are the steps to import the NinjaOne connection package.
Download the connection package.
Navigate to Admin → Transport → select Import Package.
Browse the downloaded package and Import.
Navigate to Admin → Connections → Select “NinjaOne ” Connection.
Edit the connection with your NinjaOne tenant details.
The security system represents the connection between EIC and the target application. For more information on creating a security system, see Creating a Security System.
Endpoint refers to the target application used to provision accounts and entitlements (access). For more information on creating an endpoint, see Creating Endpoints.
You can use the NinjaOne integration for performing import and provisioning operations after configuring it to meet your requirements.
You must apply the following guidelines for configuring import:
Run account import before running the access import.
Map all NinjaOne attributes to EIC account attributes using ImportAccountEntJSON.
You must apply the following guidelines for configuring provisioning:
Use Java ternary operators if you want to add conditions in the provisioning parameters. You can use Java operations to tweak any attributes by using if-else conditions, substrings, or operators in the JSON for provisioning.
To troubleshoot common problems with connectors, answer frequently asked questions, and provide solutions to a few common issues you might encounter while configuring or working with connectors, see Common Troubleshooting Guide for Connectors.
To troubleshoot common problems or obtain answers for frequently asked questions for REST connectors, see the REST Connector Guide.
Note: Ensure that you record the token expiry duration during the initial token generation. The connection may fail, if the token is not refreshed.