Where Does The Supplicant Send Identity Information?

Where does the supplicant send identity information?
The Identity information is sent to the authenticator. Now, let us know how to configure the controller and the wireless infrastructure for secure authentication.

The authentication is mostly a problem, so let us learn how to configure the controller for the classic secure authentication such as TLS. We call wireless LANs the supplicants, it is a type of authentication. The access point slash controller will not play any real role in the authentication itself, it is called the authenticator.

The authenticator is where we ask for the authentication. The clients that authenticate the clients is called authentication server. Here we have two protocols. They are X and EAP. X has a specific role, it is to allow the authenticator i.e the access point to close the radio and doesn’t allow any access to the network to the supplicants as long as the authentication server is not agreed to the authentication. So, In the authentication process, we have the supplicant asking for the authentication.

The authenticator will say eight of the eleven authentications to say yes without any question. And now the supplicant will say that it wants to move to the association phase where the authenticator will say to hold on. Now the authentication stops in order to authenticate by the authentication server. After authentication, we get a granted access and the association response. The main role of X is to block the radio for the supplicant as long as the authentication server has not been authenticated the client.

It defines some of the standard messages that are going to be exchanged between the supplicants and the authentication server. It says authenticate me and we want to check the credentials. The X is used in the combination with the EEP to perform this authentication on the wireless network.

On the other side, the clients and the supplicants are going to use 1X slash EEP dialogue with the authenticator. And this authenticator is going to translate this to the 1X slash EEP dialogue into radius in order to forward the request.

The key element is to understand is that the controller doesn’t care about what kind of 802.1X or EEP type is used as the supplicants and the authentication server. The only thing the controller cares about is if we are using the central authentication server or not. The controller must know if we are using any pre-shared key.

Every process is played between the authentication server and the supplicant. The controller mainly focuses on the key. In 1X the controller doesn’t care. Let us know the different parts of the 802.1x. They are supplicant, authenticator, and the authentication server.

The ETLs are a very secure authentication server and the supplicant both use a certificate authentication method. The server is going to send the certificate that is going to use by the clients as a key to encrypt whatever the client needs to send back to the server in an encrypted manner. so this certificate is the key and also a way for the client to authenticate the authentication server that would like to verify the authentication.