Application configurations are deployed using property list files, usually referred as “plist” files. Many MDM systems have sophisticated UI for entering app configurations but some still require raw plist format.
The following is an example of the F-Secure Elements Mobile Protection iOS configuration plist:
<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”>
<plist version=”1.0″>
<dict>
<key>configUuid</key>
<string>48222C38-65E0-4F72-9F61-11F0BE37F3C2</string>
<key>first_name</key>
<string>John</string>
<key>last_name</key>
<string>Smith</string>
<key>alias</key>
<string>JS</string>
<key>email</key>
<string>[email protected]</string>
<key>fate_registration_key</key>
<string>AAAA-BBBB-CCCC-DDDD-EEEE</string>
<key>Identifier</key>
<string>com.f-secure.mobileprotection</string>
</dict>
</plist>
Details of the elements in the file are as follows:
- configUuid – Unique version 4 UUID which identifies this configuration. UUID can be generated using public online tools
- fate_registration_key – the F-Secure Elements Mobile Protection subscription key on F-Secure Elements EPP
- Identifier – the Mobile Protection application bundle ID. This must be always com.f-secure.mobileprotection
Additional configuration items
MDM systems often have vendor-specific internal variables that can be used in the configuration. These variables are substituted with actual values about system, user, or device, when configuration is deployed to the device. Useful variables are, for example, user’s name and email address. These help administrators to identify wp-signup.phped devices on the F-Secure Elements EPP portal.
F-Secure Elements Mobile Protection supports the following optional keys:
- first_name – user’s first name
- last_name – user’s last name
- alias – user’s alternate name
- email – user’s email address
Note: The keys are case sensitive.
All MDMs may not have a suitable internal variable for all additional keys.
The following is an example how additional keys are used with MobileIron, where the following variables are available: $EMAIL$, $FIRST_NAME$, $LAST_NAME$, and $ALIAS$.<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”>
<plist version=”1.0″>
<dict>
<key>configUuid</key>
<string>48222C38-65E0-4F72-9F61-11F0BE37F3C2</string>
<key>first_name</key>
<string>$FIRST_NAME$</string>
<key>last_name</key>
<string>$LAST_NAME$</string>
<key>alias</key>
<string>$ALIAS$</string>
<key>email</key>
<string>$EMAIL$</string>
<key>fate_registration_key</key>
<string>AAAA-BB-BB-CCCC-DDDD-EEEE</string>
<key>Identifier</key>
<string>com.f-secure.mobileprotection</string>
</dict>
</plist>
Note: Major MDM vendors have established a community appconfig.org. The community has specified an XML format that goes beyond property lists, allowing application vendors to describe configuration items in different languages, define configuration data types, and describe how input is automatically validated. This XML file for Freedome for Business is available on request.