OneLogin to JSM Assets

Connect OnLink to OneLogin using OnLink - Connections tab, Add an “Other Asset Sources” connection and select OneLogin:

API URL = replace “subdomain” with your onelogin subdomain
Client ID = Follow steps here to get client id, secret
Client Secret

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:

All fields available in OneLogin’s Get User api are available for mapping. Here’s a sample mapping config:

key:id=ID
map:firstname=First Name
map:lastname=Last Name
map:email=Email
map:email=Atlassian Account ID
map:manager_user_id=ManagerObject|id=${manager_user_id}

Here’s a breakdown of some of the mapping configuration items:

Key or Map	Description

Key or Map	Description
`key:id=ID`	The keyword “key” refers to using “id” from OneLogin as a unique identifier. This allows OnLink to update the record.
`map:email=Atlassian Account ID`	Maps email from OneLogin to “User” object attribute in Assets. “Atlassian Account ID” is an attribute of type User.
`map:manager_user_id=ManagerObject\|id=${manager_user_id}`	Maps manager user id to manager object. ManagerObject is a self-referencing attribute i.e., an attribute of type object pointing to itself. This is done because a manager is also a user in OneLogin.

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.