Comment 9 for bug 41134

I can confirm this bug in Feisty (WPA Enterprise, PEAP, TKIP, using username, password, and certificate). I have to re-enter my info every time, but I also have to unlock the keyring every time. It might be writing to both gconf and the keyring (I admit I don't really know how the keyring works).

The SSID on my WPA Enterprise network that I connect to on campus has the SSID hidden (do all WPA Enterprise ones hide the SSID?), so it seems that network-manager doesn't know that the network is "there", and doesn't try to automatically connect, like it does with all of the other WPA (Personal / PSK) networks I have used. I'm not sure if this behavior is related to this particular bug.