Description of problem:
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 was not required in Mageia 2.)

Version-Release number of selected component (if applicable):
Any current version of wpa_supplicant.

How reproducible:
Attempt to connect to a WPA2 Enterprise (TLS) protected network without filling in the identity option in mcc or in wpa_supplicant.conf.

Steps to Reproduce:
1. Find a WPA2 Enterprise (TLS) protected network that you can access.
2. Configure wpa_supplicant. (certs, private key, key pass, etc. Do not configure identity.)
3. Attempt to connect to said network. (It will assoicate to the AP, but fail authentication due to missing string. As it never sends the client cert.)

As I already said this was not required in Maegia 2, and there is nothing documenting this new requirement. (wpa_supplicant's error log or debug log leaves much to be desired, as it does not mention that this was the real issue. Maybe it's supposed to generate the identity string from the client cert? Also wpa_supplicant's website also does not mention this etheir.)

This can be "fixed" by placing something in the identity string. (I used the name of the client cert plus the domain name.)


Reproducible: 

Steps to Reproduce: