Google is working to resolve authentication points affecting some ChromeOS units, that are stopping affected customers from signing into their Intelligent and ClassLink accounts.
As the corporate explains in a just lately up to date incident report on the Google Workspace Standing Dashboard, these authentication failures affect units operating model 16328.55.0 with Chrome browser model 139.0.7258.137.
These points are disrupting Single Signal-On entry to Intelligent and ClassLink academic companion platforms which might be used to handle pupil entry to digital assets.
ClassLink is utilized by over 22 million college students and employees in additional than 3,000 faculty methods throughout 50 U.S. states and 42 nations, whereas Intelligent is utilized by over 110,000 colleges, together with 95 of the most important 100 districts (roughly 60% of U.S. college students).
“Google, a service that works with Intelligent, is experiencing points with customers being unable to login utilizing their Google credentials for individuals who up to date to ChromeOS 139,” Intelligent additionally instructed customers in a separate incident report on its official standing web page.
“That is stopping customers from with the ability to login to their Intelligent account. We’re monitoring the problem and can present standing updates as they turn into obtainable.”
The identical authentication drawback additionally impacts 2-Step Verification (2SV) processes for some customers, doubtlessly blocking entry to some Google providers that require enhanced safety authentication.
Woarkarounds obtainable till a repair rolls out
Whereas its engineering groups are conducting automated testing on a possible resolution earlier than releasing the repair to affected customers, Google shared two short-term fixes that would assist these impacted work across the authentication failures.
The primary requires directors to roll again their ChromeOS set up to the earlier M138 model, utilizing the detailed directions supplied in this Google help doc.
To try this, they should undergo the next steps:
- Register with an administrator account to the Google Admin console.
- Go to Menu > Units > Chrome > Settings > Machine settings (which requires having the Cellular Machine Administration administrator privilege).
- To use the setting to all units, depart the highest organizational unit chosen. In any other case, choose a toddler organizational unit.
- Go to Machine replace settings and click on Auto-update settings.
- For Enable units to robotically replace OS model, choose Enable updates.
- For Goal model, choose a ChromeOS model.
- For Roll again to focus on model, choose Roll again OS.
- Click on Roll again OS after which click on Save.
To confirm that the affected customers’ units have efficiently rolled again, directors should check in to a managed ChromeOS gadget belonging to the organizational unit the place rollback was enabled. Then, they need to go to Settings and verify the OS model within the About ChromeOS dialog.
Alternatively, they will additionally modify the LoginAuthenticationBehavior setting to make use of “Authentication through the default GAIA stream,” which bypasses the problematic authentication pathway inflicting these ongoing failures.
“Repair is present process automated testing. As soon as accomplished, engineering will validate the outcomes and we’ll make the repair obtainable to customers,” the corporate added earlier at this time. “We at present do not have ETA for the model with the repair to be obtainable. We are going to present an replace by Thursday, 2025-08-28 17:30 US/Pacific with present particulars.”
46% of environments had passwords cracked, practically doubling from 25% final 12 months.
Get the Picus Blue Report 2025 now for a complete take a look at extra findings on prevention, detection, and information exfiltration tendencies.
