Creating an extended integration for VMware Workspace ONE assets

Integrate Oomnitza with VMWare Workspace ONE to gain visibility of your assets and desktop software, surface business critical information in dashboards and reports, and complete business processes.

See Creating workflows to learn about the integration points you can use to complete business processes.

Tip
Two integrations are available - VMware Workspace ONE UEM (API v3) and VMware Workspace ONE UEM Asset Load. Best practice is to choose the latest version which is VMware Workspace ONE UEM (API v3).

Navigation

Adding credentials to Oomnitza

Creating the integration

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.

Creating integration users

Required information

You must have the following information to complete the integration and add credentials to Oomnitza:

The URL of your instance. The format of the URL is as follows https://as<numeric_environment_value>awmdm.com. Let's say the environment variable is CN1014, then the URL is https://as1014.awmdm.com.

See Use API server URL for Workspace ONE UEM REST API calls.

Your client ID and secret which you generate in Workspace ONE. See Add an OAuth 2.0 user access token.

Your Workspace ONE UEM Token URL. The format of the URL is https://<region>.uemauth.vmservices.com.

Example: https://na.uemauth.vmwservices.com

Important
The Omnissa team is phasing out the vmwservices token URLs and replacing them with updated Omnissa URLs. When this occurs, depends on when Omnissa delivers their patch. See the Details section in Omnissa's Workspace ONE UEM article. When the customer receives the patch, they must update the Workspace ONE UEM Token URL to the values listed in the table in Section 3 Applicable changes for all Workspace ONE UEM Customers Using Token Service via Postman or Direct API in Omnissa's Workspace ONE UEM article. In Oomnitza, you update the Workspace ONE UEM Token URL in your credentials record. See screen capture.

Add credentials to the vault in Oomnitza

Create a dedicated user account for the integration instead of using an existing user account.

Adding credentials to the Oomnitza vault.

To authorize connections between Oomnitza and Workspace ONE, complete these steps:

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.

Add the information details.
Ensure that OAuth 2.0 is selected as the Authorization type.
Ensure that VMware Workspace ONE is selected from the SaaS list.
Enter the Client ID and Client Secret that was generated in Workspace ONE.
Enter the Workspace ONE UEM Token URL
Save your changes.

Creating the integration

In Oomnitza, click Configuration> Integrations> Overview.
Click Block view
Scroll down to the Extended section for asset integrations.
Click NEW INTEGRATION.
Select the integration in the sidebar.
Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

Software data

Depending on the asset integration, an option might be available to ingest desktop software information such as the name and version of the software installed on an asset. To view the software information in Oomnitza, you must have the software module.

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.

Integration details

To review or update the integrations details, click Edit .

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.

Update the integration name.
Select an installation type.
For integration preferences, select an option.
Enter the name of the integration user.

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.

Click SMART MAPPING.

You can add new fields to your integration by selecting Add new field on the mapping page.
Creating custom API fields.

Creating custom mappings

Map the Workspace ONE fields to Oomnitza fields and create custom mappings to get the information that you need.

Complete the following actions:

Click Smart Mapping to automatically map the fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
Create a custom mapping for the Device ID. To create a custom mapping, complete the following steps:
1. Click the down arrow on the ID field.
2. Select Add new Oomnitza field.
3. Change the name of the field, for example, to Device ID.
4. Select the Unique checkbox if you want to use this custom field as the sync key.
5. Click CREATE.
Select a sync key, such as the Device ID or Serial Number. The field must have unique values.
Click UPDATE.

Custom mappings

AC Line Status
Asset Number
Compliance Status
Compromised Status
Device Current Mobile Country Code
Device Friendly Name
Device SIM Mobile Country Code
Enrollment Status
ID
IMEI
Is Supervised
Last Compliance Check On
Last Compromised Check On
Last Enrolled On
Last Seen
Location Group ID
Location Group Name
Mac Address
Model
Model ID
Operating System
Ownership
Phone Number
Platform
Platform ID
Platform Name
Serial Number
UDID
User Email Address
User ID
User Name
Virtual Memory

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration.

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab.

Navigation