Sync Oomnitza with NinjaOne MSP to gain visibility of user data.
Before you start
To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application.
Information required to create the integration
To add the integration, you must enter, your NinjaOne URL. The format of the URL is https://<subdomain>.rmmservice.com.
To add credentials to Oomnitza, you must enter:
- Your client ID and secret.
- API scopes.
- Your NinjaOne URL.
When you create the application in NinjaOne, make sure Refresh Token and Authorization Code are selected as the grant types and all the scopes are selected. See API OAuth Token Configuration.
When prompted, enter this redirect URL:
https://generic-oauth2-proxy.oomnitza.com/oauth2/redirect.
Adding credentials
Make life easier and add your credentials to Oomnitza before you create the integration.
- In Oomnitza, click Configuration > Security > Credentials.
- Click Add new credential (+).
- Search for the integration, and then click the forward arrow > to select the integration.
- Enter your client credentials and any other additional information.
- Click Authenticate. You are prompted to log in to authorize your request.
- Click CREATE.
Enter scopes separated by spaces such as
monitoring management.
Adding the integration
- In Oomnitza, click Configuration > Integrations > Overview.
- Click Block view
.
- On the Integrations page, scroll down to the Extended section for user integrations.
- Click NEW INTEGRATION.
- In the sidebar, search for the integration.
- Click ADD.
Integration details overview
More information is provided about the following fields to help you complete the integration:
- User only. Add user records.
- User plus SaaS user. Add user and SaaS user records.
The benefit of adding SaaS user records is that you can run a workflow to validate the status and activity of SaaS users and retrieve information such as the role of the SaaS user. The information that can be retrieved depends on whether SaaS user workflows are available for the integration.
Installation types
- Cloud. Store credentials in the Oomnitza cloud.
- Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication.
Integration preferences
- Create & Update. Add and update records.
- Create only. Add records.
- Update only. Update records.
Editing the integration details
When you edit the Integration details section, you can select the name or names of integration contacts. Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.
- Click Edit
.
- Make your changes.
Editing the credential details
If you selected Cloud as the installation type, choose one of the following options:
- Select the credentials that were created for the integration.
- Edit the credentials that were created for the integration.
- Create new credentials
Scheduling the integration
By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.
- Click Edit
.
- Make and save your changes.
Mapping fields to Oomnitza
To map the fields to Oomnitza, click Edit .
Select Edit integration to add rules for syncing data.
Filtering integration results.
You can add new fields to your integration by selecting Add new field on the mapping page.
Creating custom API fields.
Mappable fields
Administrator
Assigned Device Ids List
Connector Sync Time
Device Ids List
Email
Enabled
First Name
Id
Invitation Status
Last Name
Mfa Configured
Must Change Pw
Notify All Clients
Organization Id
Permit All Clients
Phone
Roles List
Uid
User Type
Drag and drop
You can map additional fields to Oomnitza.
- Drag and drop the fields onto the Add new Oomnitza field area in the Oomnitza column.
- Rename the field.
- Make your changes.
- Save your changes.
Selecting sync keys
You must select at least one field as the sync key field. To ensure that the sync runs successfully, the field must contain unique values such as the serial number of an asset record or the email address of a user record. Records that do not contain a value for the sync key are skipped.
See Configuring multiple sync keys.
Comments
0 comments
Please sign in to leave a comment.