Bug 230684

Summary:	knetworkmanager does not offer to choose authentication-method for WPA EAP.
Product:	[openSUSE] openSUSE 10.2	Reporter:	Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component:	Mobile Devices	Assignee:	Helmut Schaa <hschaa>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	admin, stefan.bruens
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User --EoyBps8f 2006-12-23 12:46:36 UTC

In Yast, when configuring a WPA EAP TTLS encrypted connection I get to choose the authentication-method, default is "any". I have to choose PAP, since NetworkManager does not seem to be able to get it right on its own. (I know this because setting up the connection with Yast works without a problem whereas it stalls at 28% with NetworkManager.)

Since this prevents people from setting up their internet connection I would regard it as major and expect knetworkmanager to offer a setting to pick the method manually.

Comment 1 Forgotten User --EoyBps8f 2007-02-09 16:54:10 UTC

Are there any reasons not to provide an interface for the user in order to choose the authentication-method in knetworkmanager? Without the ability to manually choose PAP knetworkmanager is unable to handle the connection correctly.

Comment 2 Helmut Schaa 2007-03-26 14:49:46 UTC

As fas as I know, NetworkManager does not support phase2 authentications like MSCHAP or PAP yet. So we're not able to provide an user interface for now.

Tambet, any progress there? Will this be in NetworkManager 0.6.5?

Comment 3 Forgotten User --EoyBps8f 2007-03-26 18:46:40 UTC

http://bugzilla.gnome.org/show_bug.cgi?id=359369

As far as I understand it, 0.6.5 supports PAP.

Comment 4 Tambet Ingo 2007-03-27 06:34:16 UTC

Yeah, it will be in 0.6.5 when it's released.

Comment 5 Stefan Brüns 2007-05-27 13:59:07 UTC


*** This bug has been marked as a duplicate of bug 216063 ***