Bug 1120374

Matthias was trying to do a RHEL 7 install over wifi today and hit a snag.  If he chose "Red Hat" for the access point, nothing would happen.

We were expecting to see a dialog asking for PEAP, GTC, No CA Cert, etc, but instead it just showed a grayed out Configure button.

If we went to a VT to look at the anaconda messages, there was an error about "No agent available".

We were able to get it to work by running nm-connection-editor from tty2 and setting up the connection manually.

Radek says:

  We are not using nm-applet but our own SecretAgent
  which does not support wpa2 enterprise. Please file a RFE
  for RHEL.
  (https://bugzilla.redhat.com/show_bug.cgi?id=892896)

  We'd love to share the code (use nm-applet) in this case,
  we tried to integrate it in installer environment but finally
  we had to go with our own SecretAgent.
  IIRC the main reason was that the installer not being normal desktop
  environment with common wm function (but taking over
  all the desktop as one application) we wouldn't be able to
  control stacking of dialog widgets of another processes
  reasonably (in a similar way as with nm-c-e at the moment
  - the issue of dialog getting hidden behind anaconda UI 
  when clicking outside the dialog).
  There might have been other reasons as well.

  This may get better with present changes by David Shea
  (run anaconda in one window) in master. For nm-c-e it will
  be improved by adding modality option:
  https://bugzilla.redhat.com/show_bug.cgi?id=1097883

  So to move forward here, there are some options:

  - re-try harder to use nm-applet in installer
  - add support for wpa2 enterprise to our SecretAgent
  - allow to add the connection manually using nm-c-e from GUI,
     ie integrate workaround Ray used into GUI via
     existing [+] button which serves for adding virtual devices/connections
     (vlan, bond, team) currently.