Re: eap-ttls/mschapv2 versus eap-peap/mschapv2 behaviour

Olivier Beytrison wrote:

in authorize, when eap (eap_peap) return "handled", the ldap module is executed, and adds attributes to the reply. It the goes to authenticate and EAP is called again, but only eap and peap_mschapv2 are executed, not eap_peap.

I'm not sure what that means. There's EAP-MSCHAPv2, but not peap-mschapv2. And EAP-MSCHAPv2 runs inside of PEAP. So the code should always go EAP -> PEAP -> EAP-MSCHAPv2. Alan DeKok.