Export (0) Print
Expand All

3.2.1 Abstract Data Model

This section describes a model of possible data organization that a peer-side implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This specification does not mandate that an implementation adhere to this model as long as the external behavior of the implementation is consistent with what is described in this specification.

The peer maintains the current state of the authentication in an integer variable called currentState. The currentState variable is initialized to EAP_CHAP_BEGIN when the client starts the EAP-CHAP authentication, and remains valid until the authentication is completed. At any point in time, the currentState variable can have one of the following values, each one representing the current state of the client machine.

  • EAP_CHAP_BEGIN

  • EAP_CHAP_CHALLENGE_RESPONSE_SENT

  • EAP_CHAP_SUCCESS_RESPONSE_SENT

  • EAP_CHAP_FAILURE_RESPONSE_SENT

  • EAP_CHAP_SUCCESS

  • EAP_CHAP_FAILED

2f3e71e5-bd09-4ca8-90f6-559125d79ab6

Figure 3: EAP-CHAP Peer State Machine

 
Show:
© 2014 Microsoft