Hi
Our testing of the new DisableAssociationMACRandomizatio n attribute on the Wi-Fi payload for IOS 14 devices shows that when the attribute is set to false, the device will report the actual value of the MAC address to the router, but we were surprised to see that the end user can enable Private address from the device for that Wi-Fi. Doesn't this defeat the purpose of the MDM requesting that the DisableAssociationMACRandomization be enabled? Is this the correct behavior? Our mutual customers who use products like Cisco ICE need the actual MAC address which I assume is why Apple provided the new attribute DisableAssociationMACRandomization to disable the randomization feature in the first place. But if the end user can just reenable it themselves this new attribute is only marginally helpful. Are there plans to allow MDM to lock this setting?
Our testing of the new DisableAssociationMACRandomizatio n attribute on the Wi-Fi payload for IOS 14 devices shows that when the attribute is set to false, the device will report the actual value of the MAC address to the router, but we were surprised to see that the end user can enable Private address from the device for that Wi-Fi. Doesn't this defeat the purpose of the MDM requesting that the DisableAssociationMACRandomization be enabled? Is this the correct behavior? Our mutual customers who use products like Cisco ICE need the actual MAC address which I assume is why Apple provided the new attribute DisableAssociationMACRandomization to disable the randomization feature in the first place. But if the end user can just reenable it themselves this new attribute is only marginally helpful. Are there plans to allow MDM to lock this setting?
