Uploaded image for project: 'SEBA'
  1. SEBA
  2. SEBA-34

Operational Status 802.1x Authenticator

    XMLWordPrintable

    Details

      Description

      Operational Status 802.1x Authenticator

      Retrieved Parameters

      1) Current PAE Authenticator State Machine Status

      Initialize Disconnected Connecting Authenticating Authenticated
      Aborting Held Force Authentication Force Unauthentication  

      As per current implementation, AAA State Machine has only following states.

      Idle, Started, Pending, Authorized / Unauthorized.

      Map above mentioned state to implemented state machin

      ·         Initialize – Started (implemented in Jira seba-35, Number of transitions to connecting due to start request)

      ·         Disconnected – Idle (will be implemented as part this JIRA)

      ·         Connecting & Authenticating – Pending (will be implemented as part this JIRA)

      ·         Authenticated – Authorized (implemented in Jira-35, Number of authenticated transitions due to successful authentication)

      ·         Aborting – No Mapping

      ·         Held – No Mapping

      ·         Force Authentication – No Mapping

      ·         Force UnAuthentication – No Mapping

      2) Current PAE Backend State Machine Status

      Request Response Success Fail Timeout Idle Initialize

      Current implementation has only one state machine and it has only following states.

      Idle, Started, Pending, Authorized / Unauthorized.

      3) Current Status of the Authenticator

      Authorized Unauthorized

      4) Current number of valid EAPOL frames received

      5) Current number of EAPOL frames transmitted

      6) Current number of start EAPOL frames received

      This is implemented as part of SEBA-35 requirement “Number of transitions to connecting due to start request”

      7) Current number of logoff EAPOL frames received

      This is implemented as part of SEBA-35 requirement Number of transitions to disconnected due to logoff request”

      8) Current number of response ID EAP frames received

      9) Current number of response EAP frames received
      This is implemented as part of SEBA-35 requirement “Number of authenticating transitions due to EAP response or identity message”

      10) Current number of request ID EAP frames transmitted

      11) Current number of request EAP frames transmitted

      12) Current number of EAPOL frames received with invalid frame type

      13) Current number of EAPOL frames received with invalid body length

      14) Most recently received protocol version

      This would make sense per session, Moving this requirement to Jira-36 where we are implementing stats per session.

      15) Most recently received source MAC address

      This would make sense per session, Moving this requirement to Jira-36 where we are implementing stats per session.

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              shubham26 shubham sharma
              Reporter:
              mg876p Michael Gasser
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: