Bug 2389 - wpa_supplicant won't connect due to bad identity.
: wpa_supplicant won't connect due to bad identity.
Status: CONFIRMED
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-28 09:25 MSD by Zombie Ryushu
Modified: 2014-10-08 16:27 MSD (History)
3 users (show)

See Also:
RPM Package: wpa_supplicant
ISO-related:
Bad POT generating:
Upstream:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zombie Ryushu 2013-07-28 09:25:34 MSD
When connecting to a WPA2 Enterprise (TLS) protected network, wpa_supplicant fails during the authentication phase with a "bad identity" error with a working config from Mageia 2. This is due to a missing identity string for the network in wpa_supplicant.conf.

This can be "fixed" by placing something in the identity string. (I used the name of the client cert plus the domain name.)
Comment 1 Aleksandr Kazantcev 2013-10-12 01:10:01 MSD
If bug still valid?
Comment 2 Zombie Ryushu 2013-12-24 05:31:25 MSK
Yes. Nothing has changed, this is a configuration issue in how Rosa Configures wpa_supplicant.
Comment 3 FirstLevel 2014-10-08 16:27:43 MSD
Please check the problem for our new release
http://mirror.rosalab.ru/rosa/rosa2014.1/iso/ROSA.Fresh.R4/