![Fortress Technologies ES210 User Manual Download Page 156](http://html.mh-extra.com/html/fortress-technologies/es210/es210_user-manual_2322466156.webp)
Bridge GUI Guide: Security Configuration
141
4.3.2.7
Local 802.1X Authentication Settings
The Bridge’s internal RADIUS server can be configured to
authenticate 802.1X supplicant credentials using two possible
EAP (Extensible Authentication Protocol) types.
NOTE:
EAP-TLS
provides a signifi-
cantly higher level of se-
curity than
EAP-MD5
.
EAP-MD5 verifies an MD5 (Message-Digest algorithm 5) hash
of each user’s password, which requires a user’s credentials to
be present in the Bridge’s local user authentication service
before the local 802.1X service can authenticate that user.
Refer to Section 4.3.3.1 for guidance.
In order to use EAP-TLS (EAP with Transport Layer Security)
public key cryptography authentication, you must import a valid
EAP-TLS digital certificate for the local service and the root CA
(Certificate Authority) certificate that signs the local server
certificate. You must also import any root CA certificate(s) used
to sign supplicant certificates, so that the local server can verify
their authenticity. Refer to Section 6.2 for guidance. In addition,
as noted below, three local server configuration settings apply
only when
EAP-TLS
is selected for
EAP Protocols
.
802.1X Authentication
- turns the service on (
Enabled
) and
off (
Disabled
, the default).
CRL Check
- for EAP-TLS only, determines whether
certificates used to authenticate 802.1X supplicants are
checked against the lists of certificates that have been
revoked by their issuing authorities.
CRL Check
is
Disabled
by default. When the function is
Enabled
, supplicant
certificate chains are traced back to a trusted root
certificate and each certificate's serial number is checked
against the contents of the issuing authority’s CRL to verify
that none of the certificates in the chain have been
revoked, as described in RFC 3280.
CRL Check
does not
apply to EAP-MD5 authentication.
Strict Check
- for EAP-TLS only, controls strict checking of
key usage and extended key usage extensions in the
authentication server certificate.
Strict Check
is
Enabled
by
default; you can turn it off by selecting
Disabled
.
Strict Check
does not apply to EAP-MD5 authentication.
TLS Cipher
- for EAP-TLS only, specifies the list of
supported cipher suites, or sets of encryption and integrity
algorithms, that the 802.1X service will accept:
All
- the default, supports both
Legacy
and
Suite B
cipher
suites (below)
Legacy
- supports Diffie-Hellman with RSA keys
(
DHE-RSA-AES128-SHA and DHE-RSA-AES256-SHA
)
Suite B
- supports Diffie-Hellman with ECC keys
(
ECDHE-ECDSA-AES128-SHA and ECDHE-ECDSA-
AES256-SHA
)