Content Comparison

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

config:data_source

OnLink calls the “users” API by default. However this data_source config parameter allows you to change the API to any other Okta API. Here’s an example to get device info:

key:id=DeviceID
map:profile.displayName=Device Name
map:profile.platform=Device Platform
map:profile.manufacturer=Device Manufacturer
map:profile.model=Device Model
map:profile.osVersion=Device OS Version
map:_embedded.users.0.user.profile.firstName=First Name
map:_embedded.users.0.user.profile.lastName=Last Name
map:_embedded.users.0.user.profile.email=Email
config:data_source=/api/v1/devices?limit=200&expand=userSummary

Other API’s can be mapped in a similar way.

Groups:

key:id=Group ID
map:profile.name=Group Name
map:profile.description=Group Desc
config:data_source=api/v1/groups

Apps

key:id=App ID
map:label=App Name
config:data_source=api/v1/apps

Mapping User Resources - Groups, Apps

To fetch groups and apps assigned to users, use mapping below:

key:id=Username
map:profile.firstName=Firstname
map:profile.lastName=Lastname
map:user.groups=Groups|GroupID=${user.groups}
map.:user.apps=Apps|AppID=${user.apps}
config:section=groups,apps