Authentication, Figure 37 authentication settings – Raritan Computer MCIP18 User Manual

Page 50

Advertising
background image

42

M

ASTER

C

ONSOLE

IP

U

SER

G

UIDE

Authentication

Figure 37 Authentication Settings

You can use local authentication with MCIP, or store information in a central LDAP directory or
in a RADIUS server. If using LDAP or RADIUS, specify Authentication information here.

LDAP:

Type the name or IP address of the LDAP server containing all the user entries in the User LDAP
Server
field. If you use a name, you must configure a DNS server in the network settings.

Type the distinguished name (DN) where the directory tree starts in the user LDAP server in the
Base DN of User LDAP Server field.

Click on the Type of external LDAP Server drop-down arrow and choose the type of external
LDAP server. This is necessary, as some server types require special handling, and the default
values for the LDAP scheme are set appropriately. Choose Generic LDAP Server, Novell
Directory Service,
and Microsoft Active Directory. If you have neither a Novell Directory
Service nor a Microsoft Active Directory, choose Generic LDAP Server and edit the LDAP
scheme (see below).

Type the name of the attribute containing the unique login name of a user in the Name of login-
name attribute
field. Leave this field empty to use the default value (the default depends on the
selected LDAP server type).

Type the object class that identifies a user in the LDAP directory in the Name of user-entry
object class
field. Leave this field empty to use the default value (the default depends on the
selected LDAP server type).

Type a subfilter to refine the search for users known to the MCIP in the User search subfilter
field.

Type the active directory domain configured in the Microsoft Active Directory server in the
Active Directory Domain field. This option is valid only if you have chosen Microsoft Active
Directory as the LDAP server type.

RADIUS (Remote Authentication Dial In User Service):

RADIUS is a protocol specified by the Internet Engineering Task Force (IETF) working group.
There are two specifications that make up the RADIUS protocol suite: Authentication and
Accounting. These specifications aim to centralize authentication, configuration, and accounting
for dial-in services to an independent server. The RADIUS protocol exists in several
implementations, such as freeRADIUS, open-RADIUS, or RADIUS on UNIX systems. The

Advertising