Cyclades AlterPath KVM 16, Руководство пользователя

Страница: 197 / 206

B:
KVM Remote Authentication
AlterPath KVM Manual B-1
This section provides some guidelines for configuring remote authentication
in the KVM using LDAP and Kerberos. It attempts to address the unique
implementation requirements of each protocol from different platforms.
It is assumed that the user already has a fully functional authentication server
in place, an administrator who can manage the server, and the username and
password for the server has been already configured.
The authentication server administrator must add the KVM/net user, admin ,
to the authentication server. This is to enable the admin user to log in and
manage the KVM properly when they are not using local authentication.
Cyclades recommends that the local password and the remote authentication
server password be different. Using the same password will not signal a
failure of the authentication server and can mislead the administrator because
the user will always authenticate.
Remotely authenticated users need not exist in the local KVM user database
since they are added automatically with READ/WRITE access to all ports on
the KVM. The added users, however, cannot authenticate locally even after
entry in the local user database. The system grants local access only if a local
password has been set for the user.
LDAP
Regarding LDAP, the KVM web management interface assumes that the
distinguished name of the search base is:
“Ldap Base Domain Name” or “ dc= ”
For configurations that use “Organization” or “ o= ” the admin user must edit
the configuration file (/etc/ldap.conf) using vi /etc/ldap.conf and modify the
line to “ base o= ...” from “ base dc= ....”