It makes sense until the user has no clue that removing the lock totally hoses
their device and they have to call the help desk.
Ryan Turner
Manager of Network Operations, ITS
The University of North Carolina at Chapel Hill
+1 919 274 7926 Mobile
+1 919 445 0113 Office
On Feb 9, 2018, at 1:20 PM
Kind of makes sense though doesn’t it? Why would you want to allow a device
unique private key to be used without requiring a device unlock?
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
on behalf of "Turner, Ryan H"
Reply-To: The EDUCAUSE Wireless Issues Constituent Group Li
For TLS, Android requires a screen lock, and if you remove it post, it breaks
the certificate store. That issue isn’t a bug, but another design decision by
Google (to make TLS more difficult to use when it isn’t that way with almost
every other operating system).
From: The EDUCAUSE Wireless Is
I know there was a bug corrected in SecureW2 802.1X onboarding where they were
requiring a screen lock for Android when using PEAP=MSCHAPv2.
They corrected the issue in a later release.
Bruce Osborne
Senior Network Engineer
Network Operations - Wireless
(434) 592-4229
LIBERTY UNIVERSITY
Trainin
