Ivanti to JSM Assets (Beta)
- Girish Reddy
Connect OnLink to Ivanti using OnLink - Connections tab, Add an “Other Asset Sources” connection and select Ivanti:
API URL = Tenant hostname URL e.g. https://nvuprd-sfc.ivanticloud.com
Client ID = Follow steps here to get client id, secret, tenant id and tenant hostname
Client Secret
Ord Id = Tenant ID
Please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping. Here’s an example configuration:
Here’s a sample mapping config:
key:DiscoveryId=IDmap:DisplayName=Display Namemap:OS.Version=OS Versionmap:OS.Name=OS
Here’s a breakdown of some of the mapping configuration items:
Key or Map | Description |
|---|---|
| The keyword “key” refers to using DiscoveryID from Ivanti as a unique identifier. This allows OnLink to update the record. |
| Maps DisplayName from Ivanti to Display Name text attribute |
| [Optional] Set to a valid API URL. Defaults to devices but can be changed to other Ivanti API’s e.g. Ref: https://help.ivanti.com/ht/help/en_US/CLOUD/api/PeopleDevices/neuronsplatformDevices.htm |
OnLink processes data in two steps - Get Data and Import Data. To manually test, you can click on Get Data first and then wait until you see “No more pending records. Data will be imported on next Import run.” message in Job Logs. Then, click on Import. Production runs are fully automated based on the schedule you choose.
