User guide

USER GUIDE
53
Only the “admin” account remains as a “backdoor” account. This user has
KVM.net II local access. Admin account is allowed to manage KVM.net II with
"Administrator" access privileges. However, "admin" is not permitted to connect
to Targets. This account will allow changing KVM.net II to Local authentication
mode at any time.
There is no direct access to any IP device. KVM.net II will act as a gateway.
Since the KVM.net II user accounts are kept in the local database, it can happen
that some of the local accounts do not have related LDAP objects (e.g. some user's
account might migrate to another LDAP path). To clean the local database from
those ghost accounts that will never pass LDAP authentication, KVM.net II
provides the customers with the manual synchronize operation.
Users Groups will not be deleted and will be managed locally after its import.
When changing KVM.net II to Local authentication mode, all the users appear as
“inactive”. To re-activate the users, the Administrator must explicitly provide each
account with a local password.
9.3.2.2 DNS setting in LDAP mode
Important! The correct DNS setting is vital for the successful configuration of the
KVM.net in LDAP mode. You set the KVM.net DNS settings in the Settings / Unit
Maintenance / Network tab. See section 16.2 on page 114.
9.3.2.3 LDAP settings
1. Select the External Authentication tab, the LDAP settings appears, see Figure
47.
Figure 47 LDAP settings
2. Select the Use LDAP authentication server checkbox.
3. Input details of the Active Directory: