iPads Being Recognized as Mac OS X

[Anonymous]

We have noticed lately that iPads in our environment have been coming across as Mac OS X (10.15) devices in Cloudpath. This severely breaks some of the workflow processes that we've created. Here is the official response by Apple regarding this. Is this change on your roadmap? Are your developers even aware of this occuring?

Thank you for contacting us regarding this observation. This is indeed an excellent question. I understand that you are looking for confirmation if it is indeed expected that iPads running iOS 13 present a desktop User-Agent. During one of the WWDC 2019 sessions earlier this year Apple outlined that these devices would use a desktop User-Agent to provide users with a desktop experience.

The same presentation, encouraged developers away from relying on this string to uniquely identify device types.

Introducing Desktop-class Browsing on iPad
https://developer.apple.com/videos/play/wwdc2019/203/

“you should use feature detection instead of user agent sniffing.

In the past, some developers have wanted to know the user agent to specifically identify iPad, but our new desktop user agent on iPad will prevent you from doing this.”

If indeed the infrastructure is dependent on this user agent string, this will need to change as the device now presents the same string as macOS.

[michael_brado]

Thanks EOTE,

We heard about this and documented in the Cloudpath 5.5 Release Notes: https://support.ruckuswireless.com/documents/2997-cp_es-5-5-4464-ga-release-notes

 

Important Information About iOS 13 and macOS 10.15

The upcoming releases of iOS 13 and macOS 10.15 have introduced some changes that will cause some different behavior for devices running these versions compared to their behavior with Cloudpath 5.4 or earlier:



• iOS 13:

– What Has Changed (iPAD only): iPads running iOS13 identify themselves as a Mac, as opposed to a mobile device.

– Behavior in Cloudpath 5.5: The client is provided with the option of selecting the type of device (Mac or iPhone/iPad).

– Behavior in Cloudpath 5.4 or earlier: AniPad is identified to have a MacOS. Download of the executable to the iPad will fail.



– Recommendation: Upgrade to Cloudpath 5.5 for proper behavior.



– Workaround in case you prefer to remain on Cloudpath 5.4 or earlier:

1. In the Cloudpath UI, go to&onfiJuratLons > Device &onfiJuratLons.

2. Click the arrow to expand the deviceconfiguration.

3. Click the OS Settings tab.

4. In Mac OS X Settings, click the pencilicon to edit the "User experience options."

5. From the Load Preference drop-downlist, select Use MobLlHconfiJ *.

6. Click Save

When the iPad connects, the enrollment portal displays the message: "Download for MacOSX." Users can proceed with the download, and the appropriate mobileconfig gets installed.



• macOS 10.15:

– What Has Changed: There are some new requirements for attributes within a zip file.

– Behavior in Cloudpath 5.5: These attributes are set properly in the zip files to download.

– Behavior in Cloudpath 5.4 or earlier:These attributes will not be correct in older versions of Cloudpath; download

of the executable to client devices will fail.



– Recommendation: Upgrade to Cloudpath 5.5 for proper behavior.



– Workaround in case you prefer to remainon Cloudpath 5.4 or earlier:

1. In the Cloudpath UI, go to&onfiJuratLons > Device &onfiJuratLons.

2. Click the arrow to expand the device configuration.

3. Click the OS Settings tab.

4. In Mac OS X Settings, click the pencil icon to edit the "User experience options."

5. From the Load Preference drop-downlist, select Use MobLlHconfiJ *.

6. Click Save

When the device connects, the enrollment portal displays the message: "Download for Mac OS X." Users can

proceed with the download, and the appropriate mobileconfig gets installed.

[Anonymous]

Thanks! .. I must have glossed over that when we updated to the latest. This is referencing mobileconfig. But in our environment, we have a OS filter in the workflow - so that won't work for us.

Is there a work around other than adding Mac OS X into the filter (which obviously allows Mac computers to see the options as well)?