Extended integrations overview

Extended integrations allow you to connect Oomnitza with a wide range of applications and systems, so you can get a more complete view of your technology landscape.

Contents

1. Types of extended integrations
2. Data that can be synced using extended integrations
3. Creating extended integrations
4. Integration options: Cloud or Local

Note
There are fees associated with integrations. For questions on pricing, please contact your Oomnitza account manager, or reach out to [e-mail].

Types of extended integrations

There are two types of extended integrations: 

• Vendor integrations are pre-defined easy-to-use integrations that are available for a variety of applications. For a list of vendor integrations, refer to the Integration list.
• Custom extended integrations are integrations that you create yourself. They allow you to sync any data that you need from the external application to Oomnitza.

Data that can be synced using extended integrations

Vendor integrations

The following information can be synced with our vendor extended integrations:

Asset extended integrations

Creates asset records in the Oomnitza Asset module. Depending on the vendor application, the software associated with the asset can also be retrieved.

User extended integrations 

Creates user records in the Oomnitza User object. This object is the primary page for user data and where all user data is stored.

If you also chose User plus SaaS User during the integration creation process, it will additionally create SaaS user records on the Software > SaaS page. The benefit of adding SaaS user records is that you can run a SaaS user workflow to validate the status and activity of SaaS users and retrieve information such as the role of the SaaS user. The information that you can retrieve about SaaS users depends on the availability of SaaS user workflows for the integration.

Vendor extended integrations

Custom extended integrations

The following information can be synced with our custom extended integrations:

Custom extended integration

Creating extended integrations

Vendor integrations

To create a vendor integration, you can do either of the following:

Go to Configuration > Integrations > Overview and select block view  In the Extended section for assets or users, click New integration.

Go to Configuration > Integrations and click + Add in the upper right of the page. Select Assets or Users from the list.

Custom extended integrations

To create a custom integration, go to Configuration > Integrations and click + Add in the upper right of the page. Select the object from the list. 

If you select Assets or Users from the list, make sure to click Add custom to begin creating your custom integration.

Integration Options: Cloud or Local

When creating the extended integration, you have the choice between two installation types: Cloud or Local.

Cloud

With a cloud installation, you create and store your credentials securely in the Oomnitza vault. The advantage of choosing a cloud installation is that your credentials are encrypted and stored in a highly secure environment. Additionally, this setup allows you to leverage various types of authentication methods, such as AWS or OAuth, providing flexibility and compatibility with different systems and services.

Creating a vendor extended integration in the cloud

Creating a custom extended integration in the cloud

Local

With a local installation, your credentials are stored on your own virtual machine or server.

Note
AWS and OAuth are not supported for local installations.

Creating a vendor extended integration locally

Creating a custom extended integration locally