User's Manual

user name from the Intel PROSet/Wireless utility and ignores the
Authentication Protocol MS-CHAP-V2 user name. This feature is the 802.1x
identity supplied to the authenticator. Microsoft IAS RADIUS accepts only a
valid user name (dotNet user) for EAP clients. Enter a valid user name
whenever 802.1x MS RADIUS is used. For all other servers, this is optional,
therefore, it is recommended that you no use a true identity, but instead the
desired realm (for example, anonymous@myrealm).
Configure Roaming Identity to support multiple users:
If you use a Pre-Logon or Common connection profile that requires the roaming
identity to be based on the Windows logon credentials, the creator of the
profile can add a roaming identity that uses %username% and %domain%.
The roaming identity is parsed and the appropriate log on information is
substituted for the keywords. This allows maximum flexibility in configuring
the roaming identity while allowing multiple users to share the profile.
Please refer to your authentication server user guide for directions about how
to format a suitable roaming identity. Possible formats are:
%domain%\%username%
%username%@%domain%
%username%@%domain%.com
[e-mail]
If Roaming Identity is cleared, %domain%\%username% is the default.
Notes about the credentials: This user name and domain must match the
user name that is set in the authentication server by the administrator prior to
client authentication. The user name is case-sensitive. This name specifies the
identity supplied to the authenticator by the authentication protocol operating
over the TLS tunnel. This user identity is securely transmitted to the server
only after an encrypted channel has been verified and established.
Authentication Protocols: These parameter specifies the authentication protocols that
can operate over the TTLS tunnel. Below are instructions on how to configure a profile
that uses PEAP authentication with
GTC, MS-CHAP-V2 (Default), or TLS authentication
protocols. Generic Token Card (GTC)