27 Jan
2014
27 Jan
'14
3:31 p.m.
adrian.p.smith@bt.com wrote:
I had "eap" in my post-proxy section and removing it solves this one. I will need to re-test but, as I have:
OK. I've pushed a fix.
eap { ok = return }
In authorize section but no eap in authenticate section this should be ok?
If you're not doing EAP authentication, you don't need to list "eap" in the "authorize" section. Alan DeKok.