I have implemented an Unleashed solution with ICXs, R320s, and CloudPath SaaS.
We are a cloud native org, and using AAD as IDP for our applications.
We are using AAD with CloudPath utilizing SAML for integration and user authentication for onboarding to WiFi.
The process is simple, the user accesses the Cloudpath onbaording URL, gets redirected to AAD, authenticates, and downloads the app for the Certificate and WiFi configuration.
All our users are using Windows 10 devices.
I have noticed that when Windows boots up, it is not connecting to WiFi, after the user logs in, the WiFi connects.
I have investigated this, and found the the authentication is a user authentication, and this explains the behavior.
I would like to change the EAP-TLS to computer authentication, so that WiFi could connect before the user logs in.
Could you advise please ?
You can modify how the certificate is installed on the device by opening up:
You can change this in your device configuration. In Cloudpath admin UI, go to Configuration-->OS settings-->Windows-->Click Pencil by Configuration from the Network(s)-->Change WLAN Profile Type and Certificate Store to "Machine" and "Machine"-->Change Authentication Mode to "Machine Only"
If Authentication Mode isn't set to "Machine Only" then either it won't work pre-login or post-login with no user cert.
If you change to the settings I highlighted above, then it should work both pre and post login using the machine certificate.
Hi Pierce and Christopher,
Thank you for the reply and help!
If I'm changing to an already deployed configuration, will it affect the user that were already deployed with the User authentication ? Or it wont affect the already deployed, and only affect future deployed only with "Machine Only" ?