cclaus1

Yes, our identity provider (OmnID) was able to work with Google last spring to resolve this issue. Our QR codes now work great on both Chromebooks and iPads! We are using SSO and we are also using QR codes generated by OmnID (we are NOT using Clever badges). We do utilize Clever to sync rosters for several systems, and we also use Clever for SSO within our OmnID portal. But we just are not using the Clever badges, as we have no need for them since we are using badges generated by our own identity provider.

I think the version of Chrome on the Chromebook is significant. We did get our QR codes to work today on a Chromebook using version 63, but it did not work with 61 or 64. We'll do further testing to confirm what works or doesn't work... Thanks jmak and ADMaster for your input. I feel like we are at least making progress!

We are getting this EXACT same message "Please create a password to protect your local data." Our student and staff accounts work great on chromebooks using SAML SSO via our identity provider (OmnID). However, now we are trying to use QR codes to sign into the chromebook and our student/staff portal for the youngest students (grades K-2). The QR codes appear to work correctly with the camera, but instead of bringing up our district portal it now brings up this "Please create a password to protect your local data." screen and we can't figure out how to get rid of it. The QR code should include authentication info for the student's username and password, so why does it bring up this 'create password' screen? It's ironic because we are trying to use QR codes so the little kids won't have to type in their username and password, and now we get this screen where they have to type in their password twice. Our identity provider does not get this screen in his environment (it goes directly to the portal, as it should), so it must be something in our set up that is different. So far we don't see anything in > User Settings or > Device Settings regarding this issue, but we would be very interested in any ideas or resolutions regarding it. We have tried testing this with settings that clear local user data as well as settings that keep local user data on the chromebook. Both settings still get the same message. Thanks much for any information!!