After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703612 - saving password not functional in case of WPA & WPA2 enterprise security method
saving password not functional in case of WPA & WPA2 enterprise security method
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Reported: 2013-07-04 14:13 UTC by Smit Patel
Modified: 2018-04-03 09:02 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8

Description Smit Patel 2013-07-04 14:13:56 UTC
Following features/functionality is not working in case of WPA & WPA2 enterprise security method. (Edit connection dialog)
1) Saving password
2) Ask for this password everytime
In case of WPA & WPA2 personal security method, it works fine.
Comment 1 Jiri Klimes 2013-07-15 12:19:03 UTC
I can save password for WPA Enterprise networks in nm-connection-editor.

Could you provide more details on your issue?
1. What is your distro?
2. NM version
3. What (desktop) environment do you use?
4. Exact steps to reproduce
Comment 2 Smit Patel 2013-07-15 16:21:11 UTC
Distro: Archlinux
NM version:
Desktop env: Cinnamon 1.8.8
Steps to reproduce: 
  1) Connect to wifi network which has WPA/WPA2 enterprice security. (it wont prompt for password and won't connect to network)
  2) Open Network Manager
  3) Edit wifi network, you just tried to connect
  4) Select "Wi-Fi security" tab
  5) Change auth type to "Protected EAP"
  6) Enter username password. And save it. (It will connect to that wifi network)
  7) To connect to that network, you have to go through step 2-6 everytime. It doesn't remember password. If you select "Ask for this password every time" checkbox in edit connection dialog in step 4, it doesn't ask for password either.
Comment 3 Jiri Klimes 2013-07-19 11:26:22 UTC
This looks like an issue with a keyring. Do you have a keyring installed?
Would you grab NetworkManager logs? (I think they are in /var/log/daemon.log or in systemd journal: journalctl)
Comment 4 Tobias Mueller 2013-11-22 08:55:49 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Comment 5 Colin Macdonald 2013-11-26 12:36:11 UTC
Please reopen.

I think this is likely the downstream Fedora bug:

1)  We have gnome-keyring running.  It happens on a standard gnome3 desktop running on at least Fedora 18, 19, 20.
Also note the issue doesn't happen for home wifi where keys-XXX with WPA_PSK="clear text" are created correctly.

2)  The password is saved (in the keyring I assume) because the gnome-shell popup dialog is pre-filled with the correct password.  One just has to click "connect" and then it works.

3)  Its possible to manually create appropriate ifcfg- and keys- files, such that it connects automatically.  But the GUI doesn't do this.  Details of this workaround in a separate post.

I can probably attach relevant logs---if info is not in the downstream bug.  Let me know.
Comment 6 Colin Macdonald 2013-11-26 12:37:09 UTC

1) Put the key in a /etc/sysconfig/network-scripts/keys-XXX file:

IEEE_8021X_PASSWORD="clear text password"

2)  Edit the /etc/sysconfig/network-scripts/ifcfg-XXX file, to comment out this line as follows:

Comment 7 Colin Macdonald 2013-11-26 12:57:53 UTC
I also wonder if this is related to
Comment 8 Jeremy Nickurak 2014-04-25 16:40:56 UTC
Re-opening, based on additional information in the downstream bug.

It sounds like you're still in need of additional logs. I've copied that request there, hopefully that results in some progress.

In order to help, can you tell specifically what people would need to extract from journalctl? Maybe an example invocation that would return the correct information? Thanks.
Comment 9 mirh 2018-02-26 09:03:56 UTC
Downstream bug went EOL. 
Is this still a problem?
Comment 10 Colin Macdonald 2018-03-14 17:04:41 UTC
I cannot reproduce this, so perhaps it is not still a problem.

I tested on a new device with Fedora 27.  It was a different network (from the one I originally saw this on) but it was "WPA2 Enterprise".  The /etc/sysconfig/network-scripts/keys-CORPORATENET file was created (with the password in plaintext), presumably b/c I clicked "connect automatically" and "make available to all users".

So at least for me, it seems to functioning correctly.
Comment 11 Beniamino Galvani 2018-04-03 09:02:16 UTC
Closing as obsolete as per previous comment.