Service Graph Connector for Jamf properties

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Service Graph Connector for Jamf properties

    The Service Graph Connector for Jamf properties govern how the connector interacts with Jamf systems to import data into ServiceNow. These properties include authentication methods, data import options, and API usage choices that affect performance and data accuracy.

    Show full answer Show less

    Connection Properties

    Connection properties can be accessed and configured by navigating to All > Service Graph Connectors > Jamf > Connections in ServiceNow and selecting the desired connection. The properties control key behaviors of the Jamf connector:

    • authtype: Defines the authentication method for the connection. Options include basic (username and password), bearer (default, uses token retrieved via username and password), and oauth (Client credentials with client ID and secret). Out-of-the-box default connections support all three, but multi-instance connections only support basic and bearer. OAuth requires guided setup.
    • importmanagedappsonly: When set to true, only managed applications from Jamf are imported. Defaults to false, which imports all applications.
    • isdeltaenabledforcomputers: Enables delta imports for computer records when set to true, reducing import volume by only pulling changes since the last import. Available only if usejamfproapi is true. Defaults to false (full imports).
    • isdeltaenabledformobiles: Similar to the above but for mobile device records. Enabled only if usejamfmobileproapi is true. Defaults to false.
    • usejamfmobileproapi: Determines whether the Jamf Pro API (version 11.4+) or the older Jamf Classic API is used to query Jamf mobile device records. Pro API offers better performance via pagination. Default is null.
    • usejamfproapi: Similar to the mobile API setting but for Jamf computer device records. Defaults to true to use Jamf Pro API for enhanced performance.

    Practical Implications for ServiceNow Customers

    • Choosing the correct authtype ensures secure and appropriate authentication aligned with your organization's policies and connector setup (single or multi-instance).
    • Configuring importmanagedappsonly allows control over application data volume and focus on managed assets.
    • Enabling delta imports (isdeltaenabledforcomputers and isdeltaenabledformobiles) helps optimize data synchronization performance by importing only changes instead of full datasets.
    • Selecting the Jamf Pro API over the Classic API (usejamfproapi and usejamfmobileproapi) improves data import efficiency and supports larger data sets via pagination, requiring Jamf version 11.4 or higher.

    Proper configuration of these properties enables efficient, secure, and scalable integration between ServiceNow CMDB and Jamf environments, ensuring accurate and timely asset data synchronization.

    Service Graph Connector for Jamf properties control the behavior of the connector.

    Connection properties

    These connection properties are available for the Service Graph Connector for Jamf.
    Note:
    To open the Service Graph Connection Properties [sn_cmdb_int_util_service_graph_connection_property] table for the connector, navigate to All > Service Graph Connectors > Jamf > Connections, and select the connection name. The connection properties are displayed in the Service Graph Connection Properties related list.
    Table 1. Connection properties for Service Graph Connector for Jamf
    Property Description

    auth_type

    		 Set the property to basic to use Basic authentication for the connection. This authentication type uses a user name and password.

    Set the property to oauth to use Client credentials (OAuth 2.0) authentication for the connection. This authentication type uses a client ID and client secret.

    The default Bearer token authentication type uses a user name and password to retrieve a token for subsequent connection requests.

    • Type: basic | bearer | oauth
    • Default value: bearer
    Note:
    • For an OOB default connection, any of the three authentication types can be used.
    • For additional connections (multi-instance), only the Basic and Bearer authentication types can be used. To use the Client credentials (OAuth 2.0) authentication type, follow the guided setup to configure client authentication credentials for the connection. See Configure Service Graph Connector for Jamf using the guided setup.

    import_managed_apps_only

    		 Set the property to true to import only managed application records.

    When the property is set to false, all application records are imported.

    • Type: true | false
    • Default value: false

    is_delta_enabled_for_computers

    		 Set the property to true to enable the SG-Jamf Computers data source to pull only the changes (delta) between consecutive imports.

    When the property is set to false, a full import is performed with every pull.

    Note:
    This property is available only if the use_jamf_pro_api property is set to true.
    • Type: true | false
    • Default value: false

    See Configuring data synchronization in Service Graph Connector for Jamf.

    is_delta_enabled_for_mobiles

    		 Set the property to true to enable the SG-Jamf Mobile Devices data source to pull only the changes (delta) between consecutive imports.

    When the property is set to false, a full import is performed with every pull.

    Note:
    This property is available only if the use_jamf_mobile_pro_api property is set to true.
    • Type: true | false
    • Default value: false

    See Configuring data synchronization in Service Graph Connector for Jamf.

    use_jamf_mobile_pro_api

    		 Set the property to true to use the Jamf Pro API for querying Jamf mobile device records. Set the property to false to use the Jamf Classic API.
    Note:
    The Jamf Pro API is supported by Jamf version 11.4 and higher. The Jamf Pro API supports pagination of response data and provides performance improvement compared to the Jamf Classic API.
    • Type: true | false
    • Default value: null

    use_jamf_pro_api

    		 Set the property to false to use the Jamf Classic API instead of the Jamf Pro API for querying Jamf mobile device records.

    When the property is set to true, the Jamf Pro API is used for querying Jamf mobile device records.

    Note:
    The Jamf Pro API is supported by Jamf version 11.4 and higher. The Jamf Pro API supports pagination of response data and provides performance improvement compared to the Jamf Classic API.
    • Type: true | false
    • Default value: true