Yealink Technical White Paper 802.1X Authentication
29
Appendix B: 802.1X Authentication Process
A Successful Authentication Using EAP-MD5 Protocol
The following figure illustrates the scenario of a successful 802.1X authentication process using
the EAP-MD5 protocol.
1.
The supplicant sends an “EAPOL-Start” packet to the authenticator.
2.
The authenticator responds with an “EAP-Request/Identity” packet to the supplicant.
3.
The supplicant responds with an "EAP-Response/Identity" packet to the authenticator.
4.
The authenticator strips the Ethernet header and encapsulates the remaining EAP frame in
the RADIUS format, and then sends it to the authentication server.
5.
The authentication server recognizes the packet as an EAP-MD5 type and sends back a
Challenge message to the authenticator.
6.
The authenticator strips the authentication server’s frame header, encapsulates the
remaining EAP frame into the EAPOL format, and sends it to the supplicant.
7.
The supplicant responds to the Challenge message.
8.
The authenticator passes the response to the authentication server.
9.
The authentication server validates the authentication information and sends an
authentication success message.
10.
The
authenticator passes the successful message to the supplicant.
After the supplicant is authenticated successfully, the authenticator provides network access
permissions. If the supplicant does not provide proper identification, the authentication
server responds with a rejection message. The authenticator passes the message onto the
supplicant and blocks access to the LAN.
If the supplicant is disabled or reset after successful authentication, the supplicant sends an
EAPOL-Logoff message, which prompts the authenticator to block access to the LAN.
Содержание 802.1X
Страница 1: ......
