Hi All, Currently, when the authentication using specific EAP method fails, EAP server sends the Access-Reject with EAP payload indicating result as FAILURE. Is there a way by which EAP-Server can provide the exact reason of failure in Access-Reject? I mean is there any standard or Vendor specific attribute defined to indicate the failure reason. Thanks in advance. Awaneesh __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
awaneesh kumar wrote:
Currently, when the authentication using specific EAP method fails, EAP server sends the Access-Reject with EAP payload indicating result as FAILURE. Is there a way by which EAP-Server can provide the exact reason of failure in Access-Reject? I mean is there any standard or Vendor specific attribute defined to indicate the failure reason.
No. Perhaps future changes will allow this, but it's not possible right now. Alan DeKok.
Thanks! for your response. Does' it means that standards already have a way to specify this and we have not implemeted it? I mean does Radius standard already has attribute defined for this and we need to implement this on freeradius? Thanks Alan DeKok <aland@deployingradius.com> wrote: awaneesh kumar wrote:
Currently, when the authentication using specific EAP method fails, EAP server sends the Access-Reject with EAP payload indicating result as FAILURE. Is there a way by which EAP-Server can provide the exact reason of failure in Access-Reject? I mean is there any standard or Vendor specific attribute defined to indicate the failure reason.
No. Perhaps future changes will allow this, but it's not possible right now. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
awaneesh kumar wrote:
Thanks! for your response.
Does' it means that standards already have a way to specify this and we have not implemeted it? I mean does Radius standard already has attribute defined for this and we need to implement this on freeradius?
The standards do not provide for this. Therefore no EAP implementation (client or server) permits this. Alan DeKok.
participants (2)
-
Alan DeKok -
awaneesh kumar