Integration types

Create integrations to get a unified view of the multiple and diverse vendor applications that you use in your organization to manage and monitor your software and hardware technology portfolio. When you integrate your vendor applications with Oomnitza you reduce the complexity of managing multiple disconnected management tools and you facilitate the automation of processes such as onboarding, offboarding, and other business-critical processes.

Basic integrations

Basic integrations are set up, configured, and managed on a server in your network.

You use basic integrations to sync with vendor applications that must be hosted locally on a server in your network such as Microsoft SCCM, MunkiReport, and Cisco Jasper. Unlike extended integrations, basic integrations ingest only assets, software, and user data.

Basic integrations are restricted to your server for setup, configuration and management. Consider transitioning from basic to extended integrations to avail of the following benefits: 

Basic integrations

Extended integrations

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.

There are two types of extended integrations:

➢ Vendor extended integrations

Oomnitza offers pre-defined vendor extended integrations for over 150 diverse applications, such as vendor applications for managing assets, users, desktop software, SaaS apps and services, and much more.

They allow you to synchronize data from the external application to the asset or user object in Oomnitza. 

Using vendor integrations, you can easily connect Oomnitza with the applications that you already use, with minimum setup. 

For a list of vendor integrations, refer to the Vendor integration list.

➢ Universal connectors

Universal connectors give you even greater flexibility. You can use universal connectors to

• Integrate with an application that is not supported by Oomnitza or does not appear in the list of vendor extended integrations
• Transfer integration data to an object other than users or assets. 
• Transfer integration data to a custom object you have defined yourself, such as Security Certificates. 

For example, you could use a universal connector to:

• Sync inventory levels from external inventory management systems directly into Oomnitza's stockrooms and accessories object.
• Transfer security certificate data to a custom object that you have created in Oomnitza.
• Sync desktop or SaaS software information from external systems directly into Oomnitza's software object. 

Oomnitza custom extended integration

➢ Choose where you store your credentials

Extended integrations in Oomnitza offer flexibility in terms of installation options. When creating an integration, you have the choice between two installation types:

• Cloud
• Local

With a cloud installation, you create and store your credentials securely in the Oomnitza vault. This approach ensures the safekeeping of your credentials, as they are stored in a protected environment within Oomnitza's infrastructure.

With a local installation, your credentials are stored on your own virtual machine or server. This option provides you with the control and ownership of managing your credentials within your own environment.

Restriction
The option to store credentials locally is not available for integrations that require AWS or OAUTH authentication.

Service desk integrations

Service desk integrations integrate seamlessly with external ticketing systems such as FreshService, Jira, Salesforce Service Cloud, ServiceNow, and Zendesk. Users can access ticketing information and raise tickets about the devices that are managed in Oomnitza in the external ticketing system. And, users can view the tickets associated with the devices in their Oomnitza instance.

Service Desk integrations

SSO integrations

SSO integrations enable administrators to choose the identity provider that they want to use to enforce SSO authentication with their Oomnitza instance.

SSO integrations

SaaS Management integrations

You can synchronize SaaS systems with your Oomnitza instance by using login and integration information from your single sign-on (SSO) identity provider.

As well as retrieving a list of SaaS systems and SaaS users, the SaaS systems can be associated with contracts. You can gain greater insights into SaaS usage, seat availability, and user activity. Based on the analysis of the SaaS activity information, you can estimate the budgeted costs of SaaS services and determine whether you can reduce costs by unsubscribing users from SaaS systems.

In Oomnitza, you can leverage SaaS management integrations, such as Netskope to detect Shadow IT activities such as unauthorized software usage.

SaaS Management integrations

Integration partners

CDW and SHI integrations use the Oomnitza CreateAsset REST API to push asset information into Oomnitza.
 

CDW

SHI

Next steps

To explore the available integration types, click Configuration > Integrations > Overview and then click block view .