Description of problem: The Gnome GUI NetworkManger configuration app doesn't allow PKCS11 smart-cards to be used as keys and certificates. The user is forced to choose existing files. Version-Release number of selected component (if applicable): NetworkManager-openconnect-0.9.10.2-1.fc21.x86_64 How reproducible: 100% Steps to Reproduce: 1. Log in (Gnome 3) 2. choose Settings app from drop down at top left corner 3. choose Network settings 4. Add VPN (openconnect option). 5. Try to add smart card for User Certificate - forced to choose file and cannot enter correct setting pkcs11:manufacturer=piv_II;id=%01 6. Likewise for Private key Actual results: Unable to choose PKCS11 smart-card Expected results: To able to choose a smart-card Additional info: Openconect supports PCKS11 smart-cards perfectly: openconnect -v -c 'pkcs11:manufacturer=piv_II;id=%01' vpn.example.org
Yes, we should be able to use the GCR widgets for selecting a certificate, They should show the certs available in the p11-kit-configured PKCS#11 tokens, allow you to choose from them, and give back a PKCS#11 URI according to RFC7512 which specifies the cert you chose. This is all *generic* stuff, not really OpenConnect-specific. We need the same GUI widget behaviour for OpenVPN, for 802.1x, and for various other things in NetworkManager and elsewhere in GNOME. GCR does *part* of what we need, but not all of it. This ties in with https://wiki.gnome.org/Projects/NetworkManager/PKCS11 I'm going to reassign this bug to NetworkManager rather than NM-OpenConnect. For the OpenConnect case, as a workaround you can manually edit the file in /etc/NetworkManager/system-connections/xxx and set the usercert= (and userkey=) fields in the [vpn] section to be the 'pkcs11:...' URI you need.
Thanks David. For the record, it works perfectly when you just edit the config files, ie userkey=pkcs11:manufacturer=piv_II;id=%01;object-type=private usercert=pkcs11:manufacturer=piv_II;id=%01;object-type=cert I think NetworkManager needs to be restarted after the edit as this didn't work when I tried it previously. But it worked perfectly after a reboot.
(In reply to arif from comment #2) > Thanks David. For the record, it works perfectly when you just edit the > config files, ie > > userkey=pkcs11:manufacturer=piv_II;id=%01;object-type=private > usercert=pkcs11:manufacturer=piv_II;id=%01;object-type=cert > > I think NetworkManager needs to be restarted after the edit as this didn't > work when I tried it previously. But it worked perfectly after a reboot. NetworkManager doesn't have to be restarted, but you have to inform it that you changed the file and you want to reload it. You can do $ sudo nmcli con reload /etc/NetworkManager/system-connections/xxx
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.