Configuring IEEE 802.1X Authentication
The machine can connect to an 802.1X network as a client device. A typical 802.1X network consists of a RADIUS server
(authentication server), LAN switch (authenticator), and client devices with authentication software (supplicants). If a
device tries to connect to the 802.1X network, the device must go through user authentication in order to prove that
the connection is made by an authorized user. Authentication information is sent to and checked by a RADIUS server,
which permits or rejects communication to the network depending on the authentication result. If authentication fails,
a LAN switch (or an access point) blocks access from the outside of the network.
Select the authentication method from the options below. If necessary, install or register a key pair or CA certificate
before configuring IEEE 802.1X authentication (
The machine and the authentication server authenticate each other by mutually verifying their certificates. A
key pair issued by a certification authority (CA) is required for the client authentication (when authenticating the
machine). For the server authentication, a CA certificate installed via the Remote UI can be used in addition to a
CA certificate preinstalled in the machine.
This authentication method uses a user name and password for the client authentication and a CA certificate for
the server authentication. MSCHAPv2 or PAP can be selected as the internal protocol. TTLS can be used with
PEAP at the same time. Enable TLS for the Remote UI before configuring this authentication method (
TLS for Encrypted Communications(P. 287) ).
The required settings are almost the same as those of TTLS. MS-CHAPv2 is used as the internal protocol. Enable
TLS for the Remote UI before configuring this authentication method (
Communications(P. 287) ).
Start the Remote UI and log on in Management Mode.
Using CA-issued Key Pairs and Digital Certificates(P. 319) ).
Using TLS for Encrypted
Starting Remote UI(P. 326)