Assigned_To User Synchronization for Jamf

Connector Applicability

Applies to Source Connectors	Jamf
Applies to Destination Connectors	All

Assumptions

These instructions assume you have already setup a source connection in CI Sync for Jamf using the CI Sync instructions here: Add Jamf to SaaS Agent

Pre-Read

Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.

Locating and Amending the Connection Setting in the CI Sync UI

Navigate to the Settings page
Under the Source Connections heading (list), locate your Jamf connection.
Click the Update link on the right hand side of the Jamf connection.
Scroll down and locate the Section Heading and view the Individual Settings.

The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.

Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.

Setting	Type	Additional Notes
Enable Assigned To User Synchronization	Slider	When enabled: CI Sync will begin to read a config driven attribute from the source system (in this case from Jamf). The CI Sync UI will expose three additional settings as explained in the next three rows (these are the config driven attributes). For a diagrammatic view of how Assigned To user synchronization works in CI Sync (covering both the source system behaviour/settings and the destination system behaviour settings), please read the Addition Information section on this Jamf Default Config Guide page: Rule 13 - Synchronization of Assigned to User attribute for Jamf Important PII Consideration when enabling this setting When enabling this setting the CI Sync UI will warn of potential PII implications. Please read the message shown and also read Section 7 (Overview of data used within the Service) in the CI Sync Service Specification published here. Section 7 explains the impact of enabling this setting for both persisted data and transited data.
Source field for Apple Mac Devices	Choicelist	The Source Field for Apple Mac Devices provides for the selection of the specific Jamf user field attribute for Apple Mac devices that will be used to identify the user against the related ServiceNow sys_user attribute which is defined in the subsequent setting (see final row below). The choices for this setting are: Email Address User Name Real Name Extension Attribute On selecting “Extension Attribute”, a text field (Extension attribute name for Apple Mac devices) is displayed providing for the entry of the extension attribute's name. Enter the name of an extension attribute that contains the user value, e.g. ad_mail.
Source field for Mobile Devices	Choicelist	The Source field for Mobile Devices provides for the selection of the specific Jamf user field attribute for Mobile devices that will be used to identify the user against the related ServiceNow sys_user attribute which is defined in the subsequent setting (see final row below). The choices for this setting are: Email Address User Name Real Name Extension Attribute On selecting “Extension Attribute”, a text field (Extension attribute name for Mobile devices) is displayed providing for the entry of the extension attribute's name. Enter the name of an extension attribute that contains the user value, e.g. ad_mail.
ServiceNow correlation field	Choicelist	The ServiceNow correlation field defines which field in the ServiceNow sys_user table will be used to lookup the value read from the Jamf source field as defined on the prior settings (see above rows). The choices for this setting are: email User ID Name Custom Important Note for this setting You must also select the corresponding option in the ServiceNow destination connection 'User Synchronization’ section. Read this Connection Setting for more information: Define a User oriented attribute when using User Synchronization from a Source System in ServiceNow If the corresponding selection in ServiceNow is not made the sync job will error.

After modifying the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.
You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.

Importantly

Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).

For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.

Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.