Kolide to JSM Assets

Kolide to JSM Assets

Import Kolide people into JSM Assets with OnLink

Use OnLink to import people records from Kolide into Jira Service Management (JSM) Assets.

Overview

This guide explains how to configure an OnLink import from Kolide to JSM Assets. You will connect OnLink to Kolide, create an Assets import configuration, define field mappings for Kolide people data, test the import, and confirm that records are created or updated in JSM Assets.

Prerequisites

  • OnLink is installed and available in Jira from Manage your apps.

  • You have access to the target JSM Assets schema and object type.

  • You have a Kolide API URL and API key with access to the people endpoint.

  • You have reviewed the Kolide people API reference: Kolide API Overview.

Connect OnLink to Kolide

Configure the Kolide connection before creating the import mapping.

  1. In Jira, go to Manage your apps.

  2. Open OnLink, then go to Connections.

  3. Click Add System.

  4. Select Other Data Sources.

  5. Enter the Kolide API URL and API key.

  6. Save the connection.

Set up the Assets import configuration

Create the base Assets import configuration first. Review the setup guide: Assets import configuration.

After the base configuration is created, open OnLink from Manage your apps and configure the Kolide source and field-level mappings.

Configure the Kolide importer

Use the following procedure to configure the importer.

  1. Enter a descriptive name for the mapping.

  2. Set the source system to the Kolide connection you created.

  3. Confirm the Asset Schema. OnLink pre-fills this value from the JSM Assets schema where you started the configuration.

  4. Select the target Object Type for Kolide people records.

  5. Select the schedule frequency for automated production runs.

  6. Add the attribute mappings. Use the mapping example below as a starting point.

Mapping examples

People mapping

Use this mapping to import Kolide people into a JSM Assets people object type.

key:id=id map:name=Full Name map:email=Email config:api=people

Mapping reference

Use the following reference to understand each mapping entry.

Mapping item

Purpose

Notes

Mapping item

Purpose

Notes

key:id=id

Uses the Kolide id value as the unique key for the Assets object.

Required. This lets OnLink update existing records instead of creating duplicates. The target Assets attribute id should be a text attribute.

map:name=Full Name

Maps the Kolide name field to the JSM Assets attribute Full Name.

Use this when your target object type stores the person's display name or full name.

map:email=Email

Maps the Kolide email field to the JSM Assets attribute Email.

Use an Assets text attribute for email addresses, or map to another compatible attribute based on your schema design.

config:api=people

Configures OnLink to pull the list of people from Kolide.

Any supported field returned by the Kolide people API can be included in the mapping. See the Kolide people API reference.

Additional Kolide source fields

Any field available from the Kolide people API can be mapped to a compatible JSM Assets attribute.

map:<kolideFieldName>=<Assets Attribute Name>

Replace <kolideFieldName> with the field returned by Kolide and <Assets Attribute Name> with the exact JSM Assets attribute name.

Test and validate the import

OnLink processes data in two separate steps: Get Data and Import Data.

  1. Click Get Data to pull records from Kolide into OnLink staging.

  2. Open the job logs and wait for the message: No more pending records. Data will be imported on next Import run.

  3. Click Import Data to create or update people objects in JSM Assets.

  4. Review the target object type in JSM Assets and confirm that people records and attributes were imported as expected.

Production runs are fully automated based on the schedule selected in the importer configuration.

image-20240318-045922.png

Troubleshooting

Issue

What to check

Issue

What to check

No records are pulled during Get Data.

Confirm the Kolide API URL, API key, and config:api=people setting.

Records are created as duplicates.

Confirm that key:id=id is present and that the target id attribute stores the unique Kolide ID.

Attributes are blank after import.

Confirm that each mapping uses the correct Kolide field name and exact JSM Assets attribute name.