Integrations

To gain visibility into your system landscape, Oomnitza uses integrations. Oomnitza integrations sync with your organization’s existing data sources to render a true picture of your organization’s endpoints such as:

Asset endpoints
Desktop software and SaaS application endpoints
SSO and SAML endpoints

More integrations are being added daily!

Integrations are key to gaining visibility of your system landscape. The following types of integrations are available:

Extended integrations
Basic integrations
Service management integrations
API integrations for workflows
SSO (Single Sign-On) and SAML (Security Assertion Markup Language) integrations
REST API for outbound integrations
Vendor integrations
EXCEL and CSV integrations

Extended integrations

For loading large volumes of asset and user data from systems, such as JAMF and AWS on a daily schedule. To ingest the data, the external system exposes its REST API to Oomnitza.

Extended integrations can be run in the Oomnitza Cloud. Or, they can be run locally in a Docker container to access systems behind firewalls.

Basic integrations

Basic integrations are also used for loading large volumes of asset and user data from multiple systems. Unlike extended integrations, basic integrations must be installed locally. A basic integration is required for some integrations such as Microsoft SCCM, Active Directory and VMWare VCenter integrations.

Service management integrations

UI plug-in for integrating with external ticketing systems such as FreshService, Jira, Salesforce Service Cloud, ServiceNow, and Zendesk. For example, when end-users raise tickets, the plug-in enables Support to assign devices to the tickets.

API integrations for workflows

Bi-directional API for a single object, such as an endpoint or user record. You can use web services to retrieve more data about an object or send data about an object from Oomnitza to a third party system. Multiple built-in presets are available for assets, users, and SaaS users that can be used in workflows to automate complex tasks.Customers can also define their own presets in Oomnitza such as presets for Postman.

SSO and and SAML integrations

SSO and SAML allow the seamless login of a user into Oomnitza, which allows the user to bypass the login screen. JIT provisioning is also supported. It enables new users that are already validated in your SSO to access Oomnitza with a predefined role.

REST API for outbound integrations

External developers are provided with complete access to the Oomnitza data model.

To browse the officially supported REST APIs, from the menu click Configuration > Integrations > Rest APIs (Swagger Docs).

To access the REST APIs, you must insert a valid security token in the REST API header call.

Vendor integrations

Standardized push of purchasing information for new assets from vendors, such as CDW and SHI, into Oomnitza. To push purchasing information, vendors use the CreateAsset REST API.