Código HTML do Conteúdo

Post: Google shares workarounds for auth failures on ChromeOS devices - Against Invaders - Notícias de CyberSecurity para humanos.

<div> <div> Google is working to resolve authentication issues affecting some ChromeOS devices, which are preventing affected users from signing into theirClever and ClassLink accounts. As the company explains in a <a href="https://www.google.com/appsstatus/dashboard/incidents/B6TDyZ3a2dhAg59QcpZE" rel="nofollow noopener" target="_blank">recently updated incident report</a> on the Google Workspace Status Dashboard, these authentication failures impact devices running version 16328.55.0 with Chrome browser version 139.0.7258.137. These <a href="https://www.reddit.com/r/k12sysadmin/comments/1mwh8bb/unable_to_log_into_devices_that_updated_to_chrome/" rel="nofollow noopener" target="_blank">issues</a> are <a href="https://www.reddit.com/r/chromeos/comments/1mwjvys/chromeos_139_login_issues/" rel="nofollow noopener" target="_blank">disrupting</a> Single <a href="https://www.reddit.com/r/k12sysadmin/comments/1mqb1la/chromebook_sign_on_issues/" rel="nofollow noopener" target="_blank">Sign-On</a> access to Clever and ClassLink educational partner platforms that are used to manage student access to digital resources. <a href="http://www.classlink.com/" rel="nofollow noopener" target="_blank">ClassLink</a> is used by over 22 million students and staff in more than 3,000 school systems across 50U.S. states and 42 countries, while<a href="http://www.clever.com/about" rel="nofollow noopener" target="_blank">Clever</a> is used by over 110,000 schools, including 95 of the largest 100 districts (approximately 60% of U.S. students). “Google, a service that works with Clever, is experiencing issues with users being unable to login using their Google credentials for those who updated to ChromeOS 139,” Clever also <a href="https://status.clever.com/incidents/78sj7mpmtcj0" rel="nofollow noopener" target="_blank">told users</a> in a separate incident report on its official status page. “This is preventing users from being able to login to their Clever account. We are monitoring the issue and will provide status updates as they become available.” The same authentication problem also affects 2-Step Verification (2SV) processes for some users, potentially blocking access to some Google services that require enhanced security authentication. <h2>Woarkarounds available until a fix rolls out</h2> While its engineering teams are conducting automated testing on a potential solution before releasing the fix to affected users, Google shared two temporary fixes that could help those impacted work around the authentication failures. The first requires administrators to roll back their ChromeOS installation to the previous M138 version, using the detailed instructions provided in <a href="https://support.google.com/chrome/a/answer/12569990" rel="nofollow noopener" target="_blank">this Google support document</a>. To do that, they have to go through the following steps: <ol> <li><a href="https://admin.google.com/" rel="nofollow noopener" target="_blank">Sign in</a> with an administrator account to the Google Admin console.</li> <li>Go to Menu > <a href="https://admin.google.com/ac/chrome/settings/device" rel="nofollow noopener" target="_blank">Devices > Chrome > Settings > Device settings</a> (which requires having the <a href="https://support.google.com/a/answer/1219251#mobile" rel="nofollow noopener" target="_blank">Mobile Device Management</a> administrator privilege).</li> <li>To apply the setting to all devices, leave the top organizational unit selected. Otherwise, select a child <a href="https://support.google.com/a/topic/1227584" rel="nofollow noopener" target="_blank">organizational unit</a>.</li> <li>Go to Device update settings and click Auto-update settings.</li> <li>For Allow devices to automatically update OS version, select Allow updates.</li> <li>For Target version, select a ChromeOS version.</li> <li>For Roll back to target version, select Roll back OS.</li> <li>Click Roll back OS and then click Save.</li> </ol> To verify that the affected users’ devices have successfully rolled back, administrators must sign in to a managed ChromeOS device belonging to the organizational unit where rollback was enabled. Then, they should go to Settings and check the OS version in the About ChromeOS dialog. Alternatively, they can also modify the <a href="https://chromeenterprise.google/policies/#LoginAuthenticationBehavior" rel="nofollow noopener" target="_blank">LoginAuthenticationBehavior setting</a> to use “Authentication via the default GAIA flow,” which bypasses the problematic authentication pathway causing these ongoing failures. “Fix is undergoing automated testing. Once completed, engineering will validate the results and we’ll make the fix available to users,” the company added earlier today.”We currently don’t have ETA for the version with the fix to be available. We will provide an update by Thursday, 2025-08-28 17:30 US/Pacific with current details.” <a href="https://hubs.li/Q03B5Kw_0" rel="noopener sponsored" target="_blank"> <img decoding="async" alt="Picus Blue Report 2025" src="https://datalake.azaeo.com/wp-content/uploads/2025/08/blue-report-2025.jpg"> </a> </div></div>