Raritan PMC-1000, Руководство пользователя

Страница: 226 / 621

Chapter 3: Using the Web Interface
214
For security purposes, users attempting to log in to the BCM2 must be
authenticated. The BCM2 supports the following authentication
mechanisms:
•
Local user database on the BCM2
•
Lightweight Directory Access Protocol (LDAP)
• Remote Access Dial-In User Service (Radius) protocol
By default, the BCM2 is configured for local authentication. If you stay
with this method, you only need to create user accounts. See
Creating
Users
(on page 153).
If you prefer external authentication, you must provide the BCM2 with
information about the external Authentication and Authorization (AA)
server.
If both local and external authentication is needed, create user accounts
on the BCM2 in addition to providing the external AA server data.
When configured for external authentication, all BCM2 users must have
an account on the external AA server. Local-authentication-only users
will have no access to the BCM2 except for the admin, who always can
access the BCM2.
If the external authentication fails, an "Authentication failed" message is
displayed. Details regarding the authentication failure are available in
the event log. See
Viewing or Clearing the Local Event Log
(on page
313).
Note that only users who have both the "Change Authentication Settings"
and "Change Security Settings" permissions can configure or modify the
authentication settings.
To enable external authentication:
1. Collect external AA server information. See
Gathering LDAP/Radius
Information
(on page 215).
2. Enter required data for external AA server(s) on the BCM2. See
Adding LDAP/LDAPS Servers
(on page 216) or
Adding Radius
Servers
(on page 219).

For illustrations, see LDAP Configuration Illustration (on page
522) or
Radius Configuration Illustration
(on page 534).
3. If both the external and local authentication is needed, or you have to
return to the local authentication only, see Managing External
Authentication Settings
(on page 221).