Comment 20 for bug 1573720

As a workaround, I am able (at least on this 16.10 laptop) to configure an EAP-TLS connection with no problem by avoiding the buggy GUI network manager client and creating the network profile with the command line:

nmcli connection add \
 type wifi con-name "MySSID" ifname wifi0 ssid "MySSID" -- \
 wifi-sec.key-mgmt wpa-eap 802-1x.eap tls 802-1x.identity "USERNAME" \
 802-1x.ca-cert ~/ca.pem 802-1x.client-cert ~/cert.pem \
 802-1x.private-key-password "..." 802-1x.private-key ~/key.pem

I can now run `nmcli connection up MySSID` and connect to the network without error.