Bridge GUI Guide: Maintenance
205
6.2.2.2
Assigning Stored Certificates to Bridge Functions
Locally stored signed certificates can have any of three
applications on the Bridge, as indicated in the
In Use
column of
the
X.509 Certificates
list:
ssl
- the Secure Socket Layer certificate is used by the
Bridge GUI to secure browser connections to the
management interface via https (refer to Section 2.1.2).
By default, the Bridge GUI uses the automatically
generated self-signed certificate for SSL. When additional
certificates have been imported, you can change this
assignment.
IPsec
- the Internet Protocol Security certificate is used to
authenticate the Bridge as an endpoint in IPsec
transactions (refer to Section 4.2).
eaptls
- the Extensible Authentication Protocol-Transport
Layer Security certificate is used:
to authenticate EAP-TLS 802.1X supplicants—when
the Bridge’s internal authentication server is configured
to provide 802.1X authentication service (refer to
Section 4.3.2).
to authenticate an ES210 Bridge as a wireless station—
when it is dedicated to act as a wireless Client (refer to
Section 3.3.5.10).
Because Bridges used as wireless Clients must be
dedicated to the function, the EAP-TLS certificate will only
be used for one of these applications.
A given function can have only one certificate assigned to it.
You can, however, assign the same certificate to more than
one function.
To assign local certificates to Bridge functions:
1
Log on to the Bridge GUI through an
Administrator
-level
account and select
Maintain
->
Certificates
from the menu
on the left.
2
In the
X.509 Certificates
frame of the
Certificates
screen, in
the
Use
column, click the button for the relevant function:
USE
IPSEC
or
USE
EAPTLS
, to the right of the certificate you
are assigning to that function.
The button(s) for a given function will only be present if no
certificate has yet been assigned to it.