group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1107935] Re: Support for WPA Enterprise wireless networks

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>
Date: Tue, 31 Oct 2017 15:10:12 -0000
Reply-to: Bug 1107935 <1107935@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: network-manager-applet (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1107935

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  New
Status in ubiquity source package in Xenial:
  In Progress

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look for in general failure to connect to a secured wireless network when the authentication settings are correct (pre-shared key is correct), or in cases of connecting to an unsecured network.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  <http://goo.gl/2iqv6j>: "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions