So I've been attempting to tackle this issue for a couple of weeks now and have followed MANY so called fixes for this and absolutely none of them have worked. I know I must be missing something stupid and obvious here.
So we use Active Directory (AD) and 802.1x WPA/WPA2 Enterprise Wireless. What I'm wanting to accomplish is at the login screen the user will type in their credentials, the mac will then use those credentials to log into the wireless and after connecting to the wireless authenticate the AD account.
It seems that no matter what I do the mac always wants to authenticate the wireless AFTER logging in. This is useless because you cannot authenticate your login without a network connection.
I'm using OSX Server to create the configuration profile that handles the 802.1x. Also we use PEAP.
Any help on this issue would be very much apreciated as I'm at wits end with this. The only documentation I found from apple is from 10.5 when you could manually add 802.1x profiles into the network settings and they specifically said that it worked the way I wanted but I am just not getting that to happen now on 10.9 machines, using OSX configuration profiles.
So we use Active Directory (AD) and 802.1x WPA/WPA2 Enterprise Wireless. What I'm wanting to accomplish is at the login screen the user will type in their credentials, the mac will then use those credentials to log into the wireless and after connecting to the wireless authenticate the AD account.
It seems that no matter what I do the mac always wants to authenticate the wireless AFTER logging in. This is useless because you cannot authenticate your login without a network connection.
I'm using OSX Server to create the configuration profile that handles the 802.1x. Also we use PEAP.
Any help on this issue would be very much apreciated as I'm at wits end with this. The only documentation I found from apple is from 10.5 when you could manually add 802.1x profiles into the network settings and they specifically said that it worked the way I wanted but I am just not getting that to happen now on 10.9 machines, using OSX configuration profiles.