Creating an extended integration for Druva assets and users – oomnitza

Let Oomnitza be your single source of truth!

You'll get complete visibility of your assets and users as data from Druva is automatically transformed into consumable information and actionable insights.

Connect Oomnitza and Druva in minutes

Get the information and insights that you need to reduce costs and the time that you spend on administration tasks such as:

Configurable dashboards and list views of key asset and user information
Configurable reports to share information about your assets and users with your colleagues and management
Configurable asset workflows that you can easily create such as:
- Workflows for disabling, deleting, and decommissioning devices, which can also be used in workflows for offboarding users
- Workflows that ensure compliance such as workflows for upgrading the Druva install client
Configurable user workflows that you can easily create such as:
- Workflows for getting user details
- Workflows for resetting user passwords
- Workflows for preserving users
- Workflows for deleting users

Integration for Druva assets

Integration for Druva users

Before you start

Best practice
For the integration with Oomnitza, create a dedicated user account.

To collect asset and user data, you use the Druva InSync API or InSync GovCloud API.

To stream Druva data into Oomnitza, you must add your Druva OAuth 2.0 credentials to the vault in Oomnitza.

To add your credentials in Oomnitza, you'll need:

Your client ID and secret
The Druva API type

Generate Druva authentication credentials

Add the Druva API type to global settings

To save time entering information when you integrate Druva with Oomnitza and when you create workflows, you can add the Druva API type value as a global variable in Oomnitza.

In Oomnitza, click Configuration > General > Global Settings.
Click Add new variable (+).
Enter Druva.Api as the variable name.
Enter the value.
- The API type for the Druva InSync API is apis.druva. -The API type for the Druva InSync GovCloud API is govcloudapis.druva.
Click SAVE.

Learn more about Druva authorization

Add credentials to the vault in Oomnitza

To authorize connections between Oomnitza and Druva, complete these steps:

Log into Oomnitza.
Click Configuration > Security > Credentials, and then click Add new credential (+).
Add the information details.
Click the AUTHORIZATION tab.
From the Authorization Type list, select OAuth 2.0.
From the SaaS list, select Druva.
Enter your Druva client ID and secret.
Enter the API type.
Click Authenticate.
Click CREATE.

You use the credentials that you added to create and customize your Druva integrations with Oomnitza.

Extended connector integration for assets

Info and connect details

From the menu, select Configuration > Integrations and then click Integrations List View .
On the Integrations page, scroll down to the Extended section for Assets.
Click NEW INTEGRATION.
In the New Asset Integration sidebar, click Druva.
To integrate Oomnitza with the Druva InSync Asset Load, click APPLY and then click NEXT twice.

Connect page

Enter a descriptive name for the integration such as Druva Devices. That'll be the name of the user integration tile that is shown on the Integrations page.
Select Cloud as the installation type.
From the Credentials list, select the credentials from the Oomnitza vault that you added for the connection.
From the Integration Preferences list, select Create & Update.
Enter the name of the user of the integration.
Enter the API type.
Click Next.

Mappings

Map the Druva fields to Oomnitza fields and create custom mappings to get the information that you need to manage your assets.

Try it out!
Click SMART MAPPING to get a head start in mapping the fields. To map the other, you can click the down arrow in the Druva field. Select Add new Oomnitza assets field. Replace the name with a user-friendly label, and click CREATE.

Standard Druva to Oomnitza mappings

Added On
Client Version
Connector Sync Time
Device ID
Device Marked Inactive
Device Name
Device OS
Device OS Version
Device Status
Last Connected
Last Upgraded On
Platform OS
Serial Number
Total Backup Data
Upgrade State
User ID
Uuid

Make sure you complete these actions, before you click NEXT:

Map the Device ID field to Oomnitza. The Device ID field is required for asset workflows.
Select a sync key such as serial number.

Want to map more fields to Oomnitza?
Contact Support, or see Mapping extended connectors.

When you've completed mapping the Druva fields to Oomnitza fields, click NEXT.

Schedule

By default, Druva asset data is streamed to Oomnitza once every day.

You can configure the schedule to meet your needs such as changing the interval or changing the time so that the data is streamed when your system isn't busy.

Configure your schedule.
Click FINISH.

Result

A new tile is created for the integration on the Integrations page.

What to do next

If you want to see what information is collected now, click the tile on the Integrations page and click RUN.

Figure: Mock-up for illustration purposes

If you want to change the integration settings, you can click a navigation link on the page, such as 4 Mappings, and edit the settings.

Tip
To view the information that is collected about your Druva assets, click Assets.

Done with configuring your connectors? Check out the presets that you can use to automate repetitive tasks.

Use API presets to create asset workflows

To reduce costs by automating repetitive and complex tasks, take advantage of the built-in presets for assets.

To add a preset to an asset workflow, complete these steps:

Click Configuration > Workflows > Assets.
Click Add (+) and enter the name and description of the workflow.
Click Add new. A Begin and End block is automatically added to the Sandbox.
Drag and drop the API block onto the Sandbox.
Click Edit on the API block.
Enter Druva to search for the presets.
Select a preset:
- Druva Delete Device
- Druva Decommission Device
- Druva Disable Device
- Druva Upgrade Install Client
Configure and save your changes.
Edit the Begin block to set the trigger for the workflow.
Connect the three blocks together.
Validate, launch, and save your workflow.