Description of problem:
Description for 802-1x certificate properties states:
Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.
However nmcli currently expects any input to be the file path (no matter whether with or without file:// prefix)
That is somewhat inconsistent with the description and the dbus api. Changing the in-nmcli description and/or allowing blobs to be added as HEX code might help this.
Version-Release number of selected component (if applicable):
nmcli only implements file path scheme at present. It seems to me that blob is not very practical for usage in a client. It may be quite cumbersome to write and also display such data. And also there are security issue with displaying that, because e.g. private certificates are sensitive.
However we can think it over and consider for 7.2. For 7.1 we could just introduce nmcli specific description saying that certificates can only be passed as file names.
The descriptions for certificate properties added - see upstream branch jk/nmcli-certs-rh1182575.
Verified (NetworkManager-1.0.4-10.el7.x86_64), that the nmcli specific description has been added to all certificate properties:
[nmcli specific description]
Enter file path to client certificate for inner authentication (optionally prefixed
Note that nmcli does not support specifying certificates as raw blob data.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.