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

[Dimitri John Ledkov]

Test packages for this fix in xenial are now available from this ppa
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3014

It is possible to enable and upgrade packages from this ppa in place,
clear the network manager status (i.e. disconnect network, edit
connections and delete it). Clear ubiquity / oem-config state and rerun
the installer.

I will push these packages to proposed, to get a proposed desktop image
out with these changes in.

Please let me know if any other images are required for this.

** Description changed:

  [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.
+ 
+ For network-manager-applet:
+ - ubiquity uses nma gir to implement above
+ - the nma gir is missbuilt in xenial, and does not have correct dependencies, thus is not usable in the same process when both NM and NMA are in use. This was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is minimal regression potential (just a rebuild) because there are no reverse dependencies of the nma gir in xenial. And there are unlikely to be any external users of nma gir on xenial, since it is broken / has wrong dependencies.
  
  ---
  
  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.)

** Changed in: network-manager-applet (Ubuntu Xenial)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to a duplicate bug report (1249295).
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:
  In Progress
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.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, thus is not usable in the same process when both NM and NMA are in use. This was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is minimal regression potential (just a rebuild) because there are no reverse dependencies of the nma gir in xenial. And there are unlikely to be any external users of nma gir on xenial, since it is broken / has wrong dependencies.

  ---

  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