This page contains important advisory notices for devices connecting to University of Washington Wi-Fi networks.
05/20/2024 – eduroam certificate expiration notices
It has already been four years since we moved to using certificate-based authentication for eduroam and user certificates are starting to expire. Users may receive a notice via email from SecureW2, our configuration utility provider, email address “notifications@securew2.com” that look similar to this:
“Hello username@uw.edu,
This is a notice that your eduroam Wi-Fi access will expire in 30 day(s).
Device:
Certificate serial:
Please re-enroll for network access here : https://onboard.wifi.uw.edu
Regards,
UW-IT Wireless Services”
These are legitimate notices and users should re-onboard their devices. It may not always be easy to know which device this is referencing; it should be referencing the device that was onboarded to eduroam the longest time ago. If you are unsure, you can: onboard all of your devices again; wait for the certificate to expire and then re-onboard; or contact UW-IT for assistance.
01/25/2022 – eduroam – UW NetID authentication being switched off
To provide enhanced security, we will be turning off the option to connect to eduroam via your UW NetID and password (EAP-PEAP), and replacing it with certificate-based authentication (EAP-TLS).
If you’re unsure if your device uses a UW NetID/password or an authentication certificate, then we recommend you go ahead and reconfigure it using our tool via onboard.wifi.uw.edu before February 1st, 2022.
08/23/2021 – Samsung One UI 3.1 update for Android 11
The latest release of Samsung One UI 3.1 for Android 11 has introduced a feature called “Deep Sleeping Apps”. This new feature is designed to stops apps from running in the background and only allows them to run when the user opens them.
This change breaks the functionality of the SecureW2 JoinNow MultiOS app and may cause the device to fail to join the eduroam Wi-Fi network.
The steps required to fix the issues are available on SecureW2s blog post, (Solved) Android 11 Samsung “Deep Sleep” Wi-Fi Connectivity Issue.
10/13/2020 – Google Android 11 December Security Update
Google’s release of the Android 11 December Security Update will likely remove the “Do not validate” option under “CA certificate” within 802.1X based Wi-Fi profiles. This may affect users who have manually configured their device for eduroam and have not installed the correct Root Certificate with validation enabled.
Android 11 users who have issues connecting to eduroam after this update should delete the “eduroam” Wi-Fi” profile and onboard via onboard.wifi.uw.edu.
Android 11 users who have onboarded their device via the onboarding tool AFTER 05/01/2020 are not affected by this change.
09/28/2020 – Apple iOS14 Private Address
Apple’s release of iOS14 brought some changes to the way your device identifies itself to Wi-Fi networks.
This change causes the device to create a Private MAC Address for each new Wi-Fi profile created. This complicates any troubleshooting support UW-IT can provide and also causes two-factor authentication via Duo to fail.
For information on turning this feature off, please visit our guide.
You can view the advisory from Apple here.
05/01/2020 – eduroam moves to EAP-TLS
Due to changes to the eduroam Wi-Fi service as of 05/01/20, users are required to re-onboard their devices. Please visit our Eduroam Onboarding Guide for step-by-step instructions or click onboard.wifi.uw.edu to onboard right away.
03/13/2020 – Problem with connecting to Wi-Fi 6 (802.11ax) Capable Access Points with Intel® Wireless Adapters Supporting 802.11ac
Certain older generation Windows-based Intel wireless adapters are unable to see Wi-Fi 6/802.11ax networks unless their drivers have been updated. This means that your device may not be able to connect to the Wi-Fi in any buildings that are running the latest generation Wi-Fi 6 Access Points.
You can view the advisory from Intel here or download the automated Intel® Driver & Support Assistant here. If the driver assistant doesn’t find your driver, you may need to manually download it from the Intel website.