[Contents] [Prev] [Next] [Index] [Report an Error]

EAP Types

The JUNOSe software has been qualified to work with the EAP authentication methods—known as EAP types—described in Table 12. Other EAP authentication methods have not been qualified with the JUNOSe software

Table 12: Supported EAP Types

EAP Type

Behavior

1—Identity

When LCP negotiation completes, PPP sends an initial EAP identity request packet to the peer. The EAP identity response packet received from the peer is forwarded to AAA. AAA forwards the response as an Access-Request to the RADIUS server hosted on the backend authentication server.

2—Notification

The JUNOSe software forwards Notification requests from the backend authentication server to the peer and Notification responses from the peer to the server. The JUNOSe software does not initiate any Notification requests or responses.

3—NAK

The JUNOSe software forwards the NAKs received from the peer to the backend authentication server.

4—MD5-Challenge

The JUNOSe software acts as a pass-through for the EAP-MD5-Challenge negotiated between the peer and backend authentication server.

13—TLS

The JUNOSe software acts as a pass-through for the EAP-TLS negotiated between the peer and backend authentication server.


[Contents] [Prev] [Next] [Index] [Report an Error]