Looking to create an extension attribute that pulls the authenticated via for a specific ssid.
The use case is, we currently allow users to connect to the corporate wifi with username and password , but it gives them a limited network connect , they cannot connect to all services.
that shows up as Authenticated via EAP-PEAP (MSCHAPv2)
we just implemented 802.1x scep cert authentication.
That shows up as Authenticated via EAP-TLS
WE plan on deploying the new configuration profile for the 802.1x but want to make sure users are connecting with the new profile and not the old one
Best answer by daniel_behan
If your Configuration Profile is set for System instead of User, then the new profile will put the SSID into the system keychain. If your users are manually joining the WiFi, their entries for the SSID are most likely in their login.keychain. I have an Extension Attribute that looks to see if someone manually joined the Corporate WiFi instead of joining via the System Configuration Profile. Replace <SSID> with the name of your Corporate WiFi.
If your Configuration Profile is set for System instead of User, then the new profile will put the SSID into the system keychain. If your users are manually joining the WiFi, their entries for the SSID are most likely in their login.keychain. I have an Extension Attribute that looks to see if someone manually joined the Corporate WiFi instead of joining via the System Configuration Profile. Replace <SSID> with the name of your Corporate WiFi.
If your Configuration Profile is set for System instead of User, then the new profile will put the SSID into the system keychain. If your users are manually joining the WiFi, their entries for the SSID are most likely in their login.keychain. I have an Extension Attribute that looks to see if someone manually joined the Corporate WiFi instead of joining via the System Configuration Profile. Replace <SSID> with the name of your Corporate WiFi.