Okta to JSM Assets

Configure the connection to Okta by going to OnLink (Manage your apps) - Connections. Then click on Add System and select “Other Assets Sources”.

Once connection is established, 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 mapping configuration. Any field available in this Okta API can be used to map to the asset attribute.

key:id=WorkerID
map:profile.email=Email
map:profile.firstName=First Name
map:profile.lastName=Last Name
map:profile.managerId=ManagerUserId
map:profile.manager=Manager Name
map:profile.department=Department

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

Key or Map	Description
`key:id=WorkerID`	The keyword “key” refers to using Worker ID as a unique identifier. This allows OnLink to update the record.
`map:profile.email=User`	Maps email to User which can be an attribute of type User
`config:search=status eq "STAGED"`	Set search filter to limit workers returned

Any other field returned by the API can be used in the mapping.

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.