I have an iOS configuration profile server that retains a copy of the certificate presented by a device during Phase III of the over-the-air provisioning profile. This certificate is used to encrypt profiles pushed when a user browses to a given interface on the server. This method of updating was adopted due to unresolved/unexplained failures using the Update Profile button itself. It has several side benefits vs the Update Profile button in any case.
The problem is that the user can only apply one update using this method because the device deletes the device credential negotiated during the OTA protocol execution after it decrypts and successfully installs the update, removing the ability to send future encrypted updates. I can think of no reason why it should destroy the device key in this scenario. It seems like the key is being incorrectly lumped with the components of the profile pushed during Phase III of the OTA and is being deleted when those components are updated. Any thoughts? _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
