4 weeks ago
So I think I have found a bug which affects Jamf Connect Login products from at least 2.29 and above.
It seems that when the disable button for the Wifi is used on the Login screen it doesn't actually disable the Wifi. The icon still shows blue and we have issues with users logging in as we have it set to only fallback to local for users when there is no network connection. However, this doesn't turn off the Wifi and the user is stuck when attached to open Wifi points that require things like captive portals and such (not pure password logins.).
So if they reboot at some location like an airport or hotel where they have been using the wifi but not authenticated to pass traffic it will just hang and not validate with our IdP nor locally.
We would like to keep policy so that when an active Wifi is there but also have the ability for users to turn off wifi completely if they have to authenticate locally.
Anyone else seeing this problem too?
a week ago
I too have encountered this issue with Jamf Connect v2.32.0. Though it seems sporadic and not consistently reproducible. Sometimes wifi can be successfully toggled off at the login screen, sometimes not... which made me suspect there was a potential configuration profile conflict...
I checked installed our configuration profiles with Low Profile and did not find any duplicate settings enforced. So for the moment I'm at a loss.
yesterday
Updates:
[PI119511] The Jamf Connect login window currently displays the following message, even while computers have an active network connection: "Wi-F networks are currently unavailable".
20 hours ago
Thanks for pushing this forward Chris_J. I have only had this issue pop up a few times over the last year or so, and seems to be mostly 1 users who has a massive amount of 'free' wifi SSID's from traveling. So it seems that sometimes it will pop on to a captive portal network (airport, hotel) when he's trying to authenticate and mess up that process, as it won't fallback to local until there is no visible network.