Google has begun a phased rollout of an updated ChromeOS (reports are of versions 154 and 150) which started on October 6 and is expected to reach all devices by October 20. We have identified that this update can cause some ClassLink sign-in attempts to return a 401 error.
Who is affected: Users on devices that have received Google update 156. Not every sign-in is affected. For districts where Google is the identity provider, this error can prevent users from signing in to the device.
Workaround: If a user sees a 401 error, refresh the page or restart the device and try signing in again. This resolves the issue in most cases.
Next steps: ClassLink engineering has identified the cause and is developing a fix, which we expect to have ready no later than Friday, October 9. We will update this page when the fix is deployed, or sooner if anything changes.
We apologize for the disruption and appreciate your patience. If the workaround does not resolve the issue, please contact ClassLink Support.
Identified
Google has begun a phased rollout of an updated ChromeOS (reports are of versions 154 and 150) which started on October 6 and is expected to reach all devices by October 20. We have identified that this update can cause some ClassLink sign-in attempts to return a 401 error.
Who is affected: Users on devices that have received Google update 156. Not every sign-in is affected. For districts where Google is the identity provider, this error can prevent users from signing in to the device.
Workaround: If a user sees a 401 error, refresh the page or restart the device and try signing in again. This resolves the issue in most cases.
Next steps: ClassLink engineering has identified the cause and is developing a fix, which we expect to have ready no later than Friday, October 9. We will update this page when the fix is deployed, or sooner if anything changes.
We apologize for the disruption and appreciate your patience. If the workaround does not resolve the issue, please contact ClassLink Support.