Try to set up TLS connection using KDE native NetworkManager.
Choose 802.1x Security tab, choose "TLS" in "Authentication:" combobox and fill all its fields, even if all key info valid, kde-nm-connection-editor does not save changes and writes to /var/log/syslog these messages
Dec 10 12:40:43 DimanNeYa NetworkManager[894]: Error setting certificate (invalid data): (1) ca-cert
Dec 10 12:40:43 DimanNeYa NetworkManager[894]: Error setting certificate (invalid data): (1) client-cert
Dec 10 12:40:43 DimanNeYa NetworkManager[894]: Error setting private key (invalid data): (1) private-key
BUT(!!!) if you accomplish all these actions in nm-applet (from package network-manager-gnome) then all start working! It will successfully create connection, this connection will be visible for kde-nm-connection-editor...
PS And even now, when connection created by nm-applet and I have working internet, I can not fill "Private Key password:" field, ie I can fill it, but after I press "Ok" all changes disgarded
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: plasma-nm 0.9.3.1-0ubuntu1~saucy1
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Dec 10 12:34:47 2013
ExecutablePath: /usr/bin/kde-nm-connection-editor
InstallationDate: Installed on 2012-11-28 (377 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plasma-nm
UpgradeStatus: Upgraded to saucy on 2013-10-18 (52 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.