802.1x Ethernet Not Automatically Connecting

[infrase2020]

Hi,

We have deployed 802.1x successfully using EAP-TLS (device Certificate) without any issues.

We've tried to replicate the same configuration on ethernet and have been unable to get the device to automatically authenticate using 802.1x. We've set the interface to "first ethernet" and "any ethernet" however this doesn't seem to make a difference. 

The only way we can get the device to connect is to go into the ethernet connection, select 802.1x and then click the connect button. We then need to select the device certificate and enter admin credentials to allow eapolclient access to system keychain. 

Does anybody know how we can do this automatically in Jamf Pro? 

TIA. 

[k3vmo]

While I can't promise I can answer - I use the same type of setup with a machine certificate.  Note that many have never got 'Any Ethernet' to work - you have to specify the adapter - most using First.

How do you receive certificates? Are the machines bound?

Do you have anything set on the Trust tab under the configuration profile?  We use a variable for the common name *.company.com - is directory authentication checked?

Have you checked with your network admin to see whether there's a failed attempt for authentication?  Depending on what they see - that should tell you how you'd need to modify the payload.