Bug 346426 - Cannot add WPA Enterprise network that uses only user name and password
Summary: Cannot add WPA Enterprise network that uses only user name and password
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networking in general (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-21 11:26 UTC by erik_hahn
Modified: 2024-12-23 18:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description erik_hahn 2015-04-21 11:26:20 UTC
My university uses the Eduroam WPA Enterprise wireless network with username and password. When I click its "connect" button in Plasma, and enter my credentials nothing happens. Selecting any certificate tricks the network manager into trying to connect but it fails (probably because there is no "right" certificate to select.)

Connecting to the network using nm-applet works. Also I can connect to it from Plasma once my credentials are stored.

Reproducible: Always

Steps to Reproduce:
1. Try to connect to a WPA Enterprise network that uses only username and password.

Actual Results:  
Nothing happens

Expected Results:  
It connects

Platform Version 4.14.7
Comment 1 Jan Grulich 2015-04-21 11:38:56 UTC
If I get it right, you press connect button on eduroam connection you see in the applet (at that time is not configured yet) and a dialog appears where you put your credentials and once you press OK button, then nothing happens? If you then try to connect again from the plasma applet, does it work?
Comment 2 erik_hahn 2015-04-21 11:44:01 UTC
On 04/21/2015 01:38 PM, Jan Grulich wrote:
> https://bugs.kde.org/show_bug.cgi?id=346426
>
> --- Comment #1 from Jan Grulich <jgrulich@redhat.com> ---
> If I get it right, you press connect button on eduroam connection you see in
> the applet (at that time is not configured yet) and a dialog appears where you
> put your credentials and once you press OK button, then nothing happens?

Exactly. I get no confirmation and the tray icon doesn't change to the 
connecting state.

> If you
> then try to connect again from the plasma applet, does it work?

No, it apparently didn't even store my credentials. After I have 
connected from nm-applet once, I can connect to plasma afterwards.
Comment 3 Jan Grulich 2015-04-21 12:07:12 UTC
(In reply to Erik Hahn from comment #2)
> On 04/21/2015 01:38 PM, Jan Grulich wrote:
> > https://bugs.kde.org/show_bug.cgi?id=346426
> >
> > --- Comment #1 from Jan Grulich <jgrulich@redhat.com> ---
> > If I get it right, you press connect button on eduroam connection you see in
> > the applet (at that time is not configured yet) and a dialog appears where you
> > put your credentials and once you press OK button, then nothing happens?
> 
> Exactly. I get no confirmation and the tray icon doesn't change to the 
> connecting state.
This should be correct, NM should automatically try to connect to it, but it seems that in your case it assumes there is something missing. I was able to reproduce it even here, with WPA2 Enterprise using LEAP method it was trying to connect it, but not with PEAP, where I guess it assumes that a certificate is missing. I don't think there is something I can do about it.

> > If you
> > then try to connect again from the plasma applet, does it work?
> 
> No, it apparently didn't even store my credentials. After I have 
> connected from nm-applet once, I can connect to plasma afterwards.
When you try edit this connection, do you see your credentials? If not, try to re-save it, just put your credentials there and save it and edit it again to check whether they are stored. If not, here are couple of things to check:
1) Check whether "networkmanagement" kded module is present in "qdbus --session org.kde.kded /kded org.kde.kded.loadedModules ".
2) Do you have KWallet enabled?
Comment 4 Jan Grulich 2016-02-04 14:03:06 UTC
Can you check whether the situation has changed with latest Plasma 5.5.x?
Comment 5 Jan Grulich 2016-10-10 07:35:34 UTC
Closing, there is no response. Re-open this bug if this is still happening with Plasma 5.6.x and newer.
Comment 6 Ben Cooksley 2024-12-23 18:23:38 UTC
Bulk transfer as requested in T17796