Extended integration for Logitech assets

Sync Oomnitza with Logitech to gain visibility of asset data.

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 connection and credential information

Review Getting Started - Enterprise API Quick Start Guide.

Connection information

You must provide the following information to add the integration:

• Organization ID. See the response to Where can I view my Sync organization's name in Sync Portal FAQs. 
• API Server URL. The default is https://api.sync.logitech.com/v1. Check the Sync Cloud API entries in Logitech's Sync portal because the API Server URL is tenant specific and might vary depending on the region. 

Adding global variables

Save time when you create integrations and run workflows by adding connection information as global variables.

1. Click Configuration > General > Global Settings.
2. Click Add new variable.
3. Add the key value, which is the name of the variable.
4. Enter the value.
5. Save your changes.

The name of the global variable for Organization ID is Logitech.OrgId.

The name of the global variable for the API Server URL is Logitech.ApiServer.

Credential information

Type of authentication: API Token.

Adding credentials

Before you start, review Generate your connection details in Sync, in 1.8 Getting Started - Enterprise API Quick Start Guide. You will need to upload these files to Oomnitza: certificate.pem and privateKey.pem.

1. Click Configuration.
2. From the Security menu, select Credentials.
3. Click Add new credential .
4. Click ADVANCED MODE.
5. On the INFORMATION tab, enter the name of the credentials.
6. Enter the owner of the credentials.
7. Click the AUTHORIZATION tab. You can enter any values for the token name and API key as mTLS is used to authenticate. 
   1. Select API Key as the type of authorization.
   2. Enter the token name. Enter any value.
   3. Enter the API key. Enter any value.
   4. From the Add to list, select Params. 
8. Click the CERTIFICATES tab.
   1. Enable Use mTLS .
   2. Select an option from the Type list.
   3. Enter a password. Required for password-protected certificates, typically for .pfx or .p12 files. It is used to decrypt the certificate, enabling its use in secure communications.
   4. Upload the certificates:
   5. For Certificate and key, upload the  certificate.pem and privateKey.pem files.
   6. For Single .pfx file, upload the PFX file.
9. Click CREATE.

Adding the integration

1. In Oomnitza, click Configuration> Integrations> Overview.
2. Click Block view .
3. Scroll down to the Extended section for asset integrations.
4. Click NEW INTEGRATION.
5. Select the integration in the sidebar.
6. 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.

1. Update the integration name.
2. Select an installation type.
3. For integration preferences, select an option.
4. 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.

1. Click Edit .
2. 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. 

Mappable fields

Connector Sync Time
Created At
Device Category
Device ID
Device Name
Firmware Version
Health Status
Hostname
IP Address
Last Seen
MAC Address
Serial Number
Status
Warranty Expiration
Warranty Type

Drag and drop

You can map additional fields to Oomnitza.

1. Drag and drop the fields onto the Add new Oomnitza field area in the Oomnitza column.
2. Rename the field.
3. Make your changes.
4. Save your changes.

Selecting sync keys

You must select at least one field as the sync key field. To ensure that the sync runs successfully, the field must contain unique values such as the serial number of an asset record or the email address of a user record. Records that do not contain a value for the sync key are skipped.   

See Configuring multiple sync keys.