ChromeOS 66 gets 802.1x passthrough authentication

[mjk]

I'm sure a lot of Chromebook schools have been waiting for passthrough wifi authentication.

 

https://chromereleases.googleblog.com/

 

 

• Adding new keyboard shortcut to move windows from display-to-display
  
• New Chrome OS Keyboard Shortcut Helper
  
• External Display Settings enhancements
  
• Enable Video Recording in Chrome Camera App
  
• Overview window animation improvements
  
• Extending more devices support for Magic Tether
  
• Picture in Picture Magnification
  
• Ability to zoom up to 20x with Chrome OS magnifier
  
• Ability to adjust full screen mag zoom level through pinch gesture
  
• Screen sharing support for Android apps installed via the Google Play Store
  
• Add Google Play into first login Opt-in window
  
• Google Play GDPR support
  
• Google Play Maximized Window support improvements
  
• Automatically pass user credentials from Chrome OS login to network 802.1x authentication
  
• Native printing support extended to Google Play applications
  
• Add Sync notice during initial sign-in
  

[bjohnny42]

Anyone get this working or find any documentation on it?

[junz]

Hi,

 

What does this feature allow you to do?

[gh5000]

If you have wireless that has 802.1x authentication ie everyone puts in an individual username and password in to get on the WiFi which might lead to user level filtering for example.

 

I'm guessing you could have a "Chromebook" WiFi that has restricted filtering that just allows the Chromebook to do the logon, after which it will Radius authenticate to a different filtering group or vlan.

 

That's my 11pm real world use case guess.

[derf]

If you have wireless that has 802.1x authentication ie everyone puts in an individual username and password in to get on the WiFi which might lead to user level filtering for example.

 

I'm guessing you could have a "Chromebook" WiFi that has restricted filtering that just allows the Chromebook to do the logon, after which it will Radius authenticate to a different filtering group or vlan.

 

That's my 11pm real world use case guess.

 

This could actually be very useful depending on your auth engines. At the moment we use smoothwall with the chromebook connect so we don't need radius to authenticate. However if we went over to other solutions then Radius auth would be a more standard id method.