Mobile Device Extension Attributes

Mobile device extension attributes are custom fields that you can create to collect almost any type of data from a mobile device.

Note: Mobile device extension attributes do not apply to personally owned mobile devices.

When you create a mobile device extension attribute, you specify the following information:

  • Type of data being collected, such as string, integer, or date

  • Inventory category in which to display the extension attribute in Jamf Pro, such as Hardware or Purchasing

  • Input type, which determines how the extension attribute is populated with data

Extension attributes can add time and network traffic to the inventory process depending on the type of data you choose to collect and the input type used to collect it.

Mobile Device Extension Attribute Input Types

You can choose to populate the value of a mobile device extension attribute using any of the following input types:

  • Text field—This displays a text field in mobile device inventory information that you can enter a value into. Only extension attributes created manually can be populated using a text field.

  • Pop-up menu—This displays a pop-up menu in mobile device inventory information from which you can choose a value. Only extension attributes created manually can be populated using a pop-up menu.

  • LDAP Attribute Mapping—This populates the extension attribute with the value for an LDAP attribute. Beginning with Jamf Pro 10.14.0, extension attributes can be mapped to multiple-value attributes from the LDAP server, such as "memberOf". When the inventory collection settings are configured to collect user and location information from LDAP, these values will be displayed in the inventory information for a device. The multiple values can later be used when creating smart groups and advanced searches with the extension attribute criteria and the “has" or "does not have” operators.
    Consider the following limitations when using LDAP multiple-value extension attributes:

    • Multiple-value attribute mapping will not work with nested groups. Only the groups directly listed on the User record will be displayed in the mapped LDAP extension attribute.

    • For the extension attributes to work correctly, values returned from the LDAP server cannot contain the sequence of repeating vertical-bar characters (ASCII code 124, HTML entity = |).

Creating a mobile device extension attribute generates a variable that can be used to populate configuration profile settings. The variable is $EXTENSIONATTRIBUTE_<#>, where <#> is the extension attribute ID. For extension attributes with the "Text field" or "Pop-up menu" input type, the ID number is found in the extension attribute URL. In the example URL below, "id=2" indicates the extension attribute ID number:

For more information on payload variables for configuration profiles, see Mobile Device Configuration Profiles.


To create a mobile device extension attribute with the “LDAP Attribute Mapping” input type, you need:

Creating a Mobile Device Extension Attribute

  1. Log in to Jamf Pro.

  2. In the top-right corner of the page, click Settings images/download/thumbnails/79168805/Icon_Settings_Hover.png .

  3. Click Mobile Device Management.

  4. Click Extension Attributes images/download/thumbnails/79168805/Extension_Attributes.png .

  5. Click New images/download/thumbnails/79168805/Icon_New_Button.png .

  6. Configure the settings on the pane.

  7. Click Save.

If the extension attribute has the “LDAP Attribute Mapping” input type, the LDAP attribute variable is displayed on the pane.

Related Information

For related information, see the following sections in this guide:

Copyright     Privacy Policy     Terms of Use     Security
© copyright 2002-2019 Jamf. All rights reserved.