Wireless stuck at validating identity interspecies dating
It has broken both our 802.1x Wifi and Ethernet connections. I EVENTUALLY got a prompt to validate a cert, but it requires Admin credentials to do so. After I got back on the network, I restarted the computer and found that reconnecting to the network is all wonky now. Only workaround that works for us is to manually go into the system keychain and set issuing and wireless certs to "always trust" (the root is already set to always trust).
Wi Fi won't even try to connect until after completely logged in and at the desktop (which means any Login triggers won't happen), Ethernet gets stuck in an infinite loop and never connects on its own. Doesn't seem to be a good way to script this since the certs are deployed via config profile and already in the system keychain (so we can't really leverage a to actually ignore the update.
To second @jasonaswell, I had to sudo the ignore command to get the update to be ignored (wouldn't need to do so from a JAMF script).
You can check whichever cert is appropriate for your environment.
Our ethernet profile has no certs in it at all because the trust is established with the certs from the wifi profile.
It gets a self assigned IP for a few seconds then falls back to "not connected" and then gets a self assigned IP... The only way I can connect via Ethernet now is to click on Disconnect, wait a few seconds then click Connect. I've also tried "mac OSSierra Update-10.12.5" "Mac OS Sierra Update (10.12.5)" "10.12.5" and "mac OS Sierra Update" to no avail.
We have update scheduled to push to clients this weekend but looks like I'm going to have to reschedule until this is fixed cause this is BAD.
At my company we import them directly to the keychain using the security command with appropriate trust options.