Hi, Following are the additional fields found in iOS MDM other than the once we find in Android. Since our table structure is little bit tight to Android platform it is necessary to identify the extension points to store these fields as well along with Windows fields.
1) Challenge - since iOS get above information in 2 steps it has a challenge password embedded in the iOS payload. This is to verify the identify of the device together with its UDID. 2) Product - for this I will be sending this as either iPhone, iPad or iPod by looking at sub-strings. 3) Serial - serial number of the device. 4) Version - iOS device type. 5) IMEI - IMEI number. Incase there is no IMEI number it will return empty (ie iPad without the sim). 6) Model - model number of the device. 7) UDID - mapping to device identifier. 8) Token, Magic token and unlock token for normal push and MDM push notifications. After the enrollment using device information command we can fetch the device information such as AvailableDeviceCapacity, BluetoothMAC, BuildVersion, CarrierSettingsVersion, CurrentCarrierNetwork, CurrentMCC, CurrentMNC, DataRoamingEnabled, DeviceCapacity, DeviceName, ICCID, IMEI, IsRoaming, Model, ModelName, ModemFirmwareVersion, OSVersion, PhoneNumber, Product, ProductName, SIMCarrierNetwork, SIMMCC, SIMMNC, SerialNumber, UDID and WiFiMAC. Please note that these fields could vary based on the OS version of the device. We need to make these fields generic which will be helpful for the MDM to fetch data accurately in generic manner as well as store them generically so that any platform can fit into the existing architecture. Regards, Dilshan -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/ https://www.linkedin.com/profile/view?id=50486426
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
