78
Here we see that an EAP request for identity is made via the Authenticator (packet 6). Jetdirect
returns a response (packet 7) and then the Authenticator returns an EAP failure (packet 8). The first
thing to check in this failure mode is the 802.1X User Name on Jetdirect. The Authentication Server
does not recognize the user name that Jetdirect is sending back.
That one was easy.
Server Authentication Problem
Once the EAP identity has been verified, the next step for both EAP-TLS and PEAP is to verify that the
authentication server is valid. This validation is done through checking the Server Certificate. Two
fields are vitally important in Jetdirect’s configuration: The server ID field in the 802.1X configuration
and the CA Certificate installed on Jetdirect.
Here we can see that the server authentication failed. We see clearly from the log that the server ID
field of JD does not match the subject name of the certificate. Let’s look at different failure, but still a
server authentication issue:
To Next Page
Loading...
Need help?
General
