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

On 18/07/13 12:55, Olivier Beytrison wrote:

Here this is, IMHO, a feature that is not working as expected.

*Which* feature?

I narrowed it down to why this happen now with EAP-PEAP/PEAP-MSCHAPv2 ...

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 sorry, I don't understand any of this.

so the fix would be to save the attributes in rlm_peap_mschapv2

Disagree, strongly.