User Manual

● If you know the server name enter this name.
● Select the appropriate option to match the server name exactly or specify the
domain name.
14. Use Client Certificate: This option selects a client certificate from the Personal
certificate store of the Windows logged-in user. This certificate will be used for
client authentication. Click the Select button to open a list of installed certificates.
● Note about Certificates: The specified identity should match the field "Issued
to" in the certificate and should be registered on the authentication server
(i.e., RADIUS server) that is used by the authenticator. Your certificate must
be "valid" with respect to the authentication server. This requirement
depends on the authentication server and generally means that the
authentication server must know the issuer of your certificate as a Certificate
Authority. You should be logged in using the same username you used when
the certificate was installed.
15. Select the certificate from the list and click OK. The client certificate information
displays under "Client Certificate".
16. Click Close.
17. Click the Finish button to save the security settings for the profile.
Setting up the Client for WPA using TKIP encryption and TTLS or
PEAP authentication
Using TTLS authentication: These settings define the protocol and the credentials used
to authenticate a user. In TTLS, the client uses EAP-TLS to validate the server and
create a TLS-encrypted channel between the client and server. The client can use
another authentication protocol, typically password-based protocols, such as MD5
Challenge over this encrypted channel to enable server validation. The challenge and
response packets are sent over a non-exposed TLS encrypted channel.
Using PEAP authentication: PEAP settings are required for the authentication of the
client to the authentication server. In PEAP, the client uses EAP-TLS to validate the
server and create a TLS-encrypted channel between client and server. The client can
use another EAP mechanism, such as Microsoft Challenge Authentication Protocol
(MSCHAP) Version 2, over this encrypted channel to enable server validation. The
challenge and response packets are sent over a non-exposed TLS encrypted channel.