User Manual

25
user name.
OR: Enter a PEAP user name in the User Name field to use a separate user
name and start the PEAP authentication process.
Check the Validate Server Identity check box to force the system to
authenticate the identity of the server as an added level of security.
Choose the certificate authority from which the server certificate was
downloaded in the Trusted Root Certification Authorities drop-down box.
Choose Token or Static Password, depending on the user database.
Note that Token uses a hardware token device or the Secure Computing
SofToken program (version 1.3 or later) to obtain and enter a one-time
password during authentication.
Click Settings and:
Leave the Specific Server or Domain field blank to allow the client to accept a
certificate from any server that supplies a certificate signed by the certificate
authority listed in the Trusted Root Certification Authorities drop-down box on
the Define PEAP (EAP-GTC) Configuration window (recommended) or enter
the domain name of the server from which the client will accept a certificate.
If the Login Name field is not filled in automatically, enter your username.
Click OK to save your settings and return to the Profile Management (Security)
window.
Click OK.
Enable the profile.
PEAP (EAP-MSCHAP V2)
To use PEAP-MSCHAP V2 security In the Atheros Client Utility, access the
Security tab in the Profile Management window.
On the Security tab, choose the WPA radio button.
OR: On the Security tab, choose the 802.1x radio button.
Choose PEAP (EAP-MSCHAP V2) from the drop-down menu.
To use PEAP (EAP-MSCHAP V2) security, the server must have WPA-PEAP
certificates, and the server properties must already be set. Check with the IT
manager.
Click the Configure button.
Check the Validate Server Identity check box to force the system to
authenticate the identity of the server as an added level of security.
Choose the certificate authority from which the server certificate was
downloaded in the Trusted Root Certification Authorities drop-down box.